Add prometheus scrape annotations to Jaeger collector, query and all-… #27
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
…in-one Signed-off-by: Gary Brown <[email protected]>
|
The prometheus discovery process makes use of the rewrite rules to determine whether a pod (or service endpoint) should be scraped, and optionally what path and port to use. Identifying the pods/service endpoints is based on its integration with kubernetes. |
dt-cloner bot
pushed a commit
to IshwarKanse/jaeger-operator
that referenced
this pull request
Jul 22, 2024
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.
…in-one
This PR allows an existing prometheus deployment to scrape the metrics from the Jaeger backend.
Currently the agent is not annotated, as only appears to be support for injecting sidecar. Will create a separate issue to explore how to annotate agent sidecar, and daemonset when supported.