-
Notifications
You must be signed in to change notification settings - Fork 35
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
Workload tracing #645
Merged
Merged
Workload tracing #645
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
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.
Issue
Add workload tracing for prometheus workload.
Solution
Use built-in tracing capabilities in Prometheus.
Context
We're also following a decision to split charm-tracing and workload-tracing into separate endpoints. If you have Tempo deployed and related with Prometheus in your production environment, please see Upgrade Notes below.
Tracing configuration Prometheus reference: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#tracing_config
Testing Instructions
Deploy the following bundle:
Upgrade Notes
Please note that the breaking change only affects you if you have Prometheus integrated with Tempo on production environments. If you haven't deployed Tempo, you're not affected.
We are rolling out the split within the COS charms. If you have COS components deployed together with Tempo and related using a
tracing
integration in your Juju model, please remove thetracing
relation before the upgrade and re-relate the applications to tempo after the upgrade.