STAC-25425: fix span duration queries - #11
Merged
Merged
Conversation
craffit
approved these changes
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The OTel stackpack span duration monitors and metric bindings were querying
otel_span_duration_milliseconds_bucket, which no longer exists when using the SUSE Observability telemetry gateway. The telemetry gateway's spanmetrics connector is configured withhistogram.unit: s, which causes the connector to emitotel_span_duration_seconds_bucketinstead - in line with the OTel semantic convention that the spanmetrics connector is transitioning to as its new default.The promql
orshould cover backward compatibility.Applied the changes to verify the span duration queries are working: