OpenTelemetry with Workflows and App

đź’¬ Workflows
1

I categorized this topic as “workflows” but it also applies to apps.

Does Retool have an “OpenTelemetry Trace ID” that’s accessible in javascript or instrumented with external resources? I’d like to send it with any logs I generate (I use sumo for log collection/aggregation), and it would be nice if Retool would include the OpenTelemetry (or jaeger) trace id header(s) in requests to external systems (ie auto instrumentation across network boundaries).

I recognize there are sentry and datadog integrations. We use sentry, but not for tracing and we don’t use datadog at all. Regardless, I don’t know if requests from retool are stitched together with requests into backend services, in Datadog or Sentry.

Right now, for logging in workflows, I include the workflow id so I can stitch some things together myself. But this still doesn’t allow me to stitch together interactions with our backend services. In theory we could add support for “workflow id” in every one of our endpoints that retool uses, but that’s not really a good solution nor viable for us.

Any ideas would be helpful.

Thanks,

Larry

3

Hi @lkiss,

Check out our docs here!

If you are self hosted, there is the WORKFLOW_TEMPORAL_OPENTELEMETRY_COLLECTOR variable that will allow for you to access more logs.

Let me know if this helps :crossed_fingers:

4

@Jack_T we’re using cloud, but thanks for chiming in.

5

Ah ok thank you for letting me know @lkiss,

It seems we do not by default pass workflow IDs to Sentry or Datadog but I can check if we have an open feature request ticket for such and will add your +1 to that.

Users have resorted to workarounds like including the workflow ID in logs to manually stitch things together, but this doesn't allow stitching interactions with backend services automatically.