Avoid exemplar labels such as {} #3266
Merged
Conversation
This file contains 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
…empty string instead Signed-off-by: tim.quinn@oracle.com <tim.quinn@oracle.com>
danielkec
approved these changes
Aug 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #3230
There can be cases in which a tracing span context exists but returns an empty label/trace ID.
In such cases, Helidon would create an exemplar with labels
{}(normally they look like{trace_id="xyz"}and that would cause errors in Prometheus.This PR detects when none of the exemplar services (only tracing provides them currently) delivers a non-empty label, and in that case suppresses the empty label expression.
Signed-off-by: tim.quinn@oracle.com tim.quinn@oracle.com