[chore] [exporter/googlemanagedprometheus] Fix invalid filter processor syntax in README example#49425
Open
vishalmore90 wants to merge 1 commit into
Open
[chore] [exporter/googlemanagedprometheus] Fix invalid filter processor syntax in README example#49425vishalmore90 wants to merge 1 commit into
vishalmore90 wants to merge 1 commit into
Conversation
Signed-off-by: vishal <httpsvishal07@gmail.com>
vishalmore90
requested review from
a team,
braydonk,
dashpole and
jsuereth
as code owners
github-actions
Bot
added
the
exporter/googlemanagedprometheus
vishalmore90
changed the title
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.
Context
Resolves #49414
The troubleshooting section of the
googlemanagedprometheusexporter README contained a syntactically invalid example for configuring thefilterprocessor. It incorrectly used a YAML list formetricsinstead of a map, causing startup failures when users copy-pasted the config.Changes
filterprocessor example to use the modern OTTLmetric_conditionsformat.metrics:map syntax withmetric_conditions:and explicitly usedmetric.name != ....Verification
filterprocessordocumentation and OTTL standards.