[Cortex] Example project #238
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
connorlindsey
requested review from
Aneurysm9,
evantorrie,
jmacd,
lizthegrey and
MrAlias
as code owners
MrAlias
approved these changes
Aug 18, 2020
|
Looks like maintainer edits is turned off here. If you can sync with master this looks ready to merge. |
…try-go-contrib into cortex-example-project
Merged
plantfansam
referenced
this pull request
in plantfansam/opentelemetry-go-contrib
Mar 18, 2022
Jaeger exporter was replaced with stdout exporter in the example, so update the README to reflect that. Also drop the screenshot - it's not referenced anywhere.
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.
This PR adds an example project to the Cortex exporter demonstrating basic usage.
It runs the following services with docker-compose:
Note: Metrics will not display at the moment. I accidentally was sending metrics with the timestamp in seconds instead of milliseconds. We'll file a fix for that today.