OpenTelemetry support for workflows

[grozdz]

Feature description

Hi All,

I have a generic suggestion about traces. In our setup, we trigger Kestra workflows from our microservices which are instrumented with Open Telemetry. This way we can observe how requests go through our infrastructure. It would be great to add possibility to instrument workflows and send traces to Open Telemetry collector, so we can see Kestra workflow as part of traces and service graph. I was told on Slack that there is no such feature so far, so I'm proposing it.

Best regards,
Grzegorz

[loicmathieu]

Hi,
Small question to pinpoint this feature request.
Do you want a Kestra workflow execution to be a single span for the whole execution or to have one span per tasks?

[grozdz]

Hi,
I think it would be great to have possibility to choose, e.g. parameterize it per flow. In our case certain flows are more complex than others, so it would be great to have visibility per task. But single span would be great option too.

[Ben8t]

As Loic has a working code already, let's keep it for 0.21.
It's a great addition! Though a different subject, it perfectly matches the theme of "Log Shipper" for the coming release cc @anna-geller

Remaining work (@loicmathieu please add additional items if needed):

• Naming convention for trace/span. Idea for now is to refer traces to the corresponding Kestra component (executor, queue, etc.)
• configuration refinement?

[Ben8t]

@loicmathieu is still manageable to have this in 0.21? Or best to move for next release?

[loicmathieu]

Yes, a PR is openned and ready to be merged.
But I have another PR that modified the same code that is opened and not ready, so I was waiting for this one to avoid too complex merge.

I'll merge everything tomorrow...