Enable Jaeger on AMI instances #131
Merged
Conversation
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
Enables Jaeger by default for AMI instances
marcleblanc2
changed the title
jdpleiness
approved these changes
Jan 3, 2025
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.
Enables Jaeger by default for AMI instances.
As the intent of the AMI is minimize configuration requirements below the web UI, deploying the Jaeger container in the AMI by default removes this step. It also results in the image getting baked into the AMI, so that customers who cannot pull images from Docker Hub can still use HTTP traces when needed to troubleshoot issues with their instance.
After / if this PR is merged, a corresponding update to the HTTP tracing docs will be made, to include the AMI https://sourcegraph.com/docs/admin/observability/tracing
Tested manually on AWS AMI