Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Mention how to redirect the Jaeger traces to a specific Jaeger instance #16531

Merged
merged 4 commits into from
Oct 23, 2023
Merged

Mention how to redirect the Jaeger traces to a specific Jaeger instance #16531

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5765330
Mention how to redirect the Jaeger traces to a specific Jaeger instance
MTRNord Oct 20, 2023
485ec6d
Add changelog for PR16531
MTRNord Oct 20, 2023
1346cc6
Improve the wording for the opentracing jaeger_agent address config
MTRNord Oct 23, 2023
6fdb0d2
Add link to opentracing configuration field in synapse to the opentra…
MTRNord Oct 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/16531.doc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Add a sentence to the opentracing docs on how you can have jaeger in a different place than synapse.
5 changes: 5 additions & 0 deletions docs/opentracing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,11 @@ docker run -d --name jaeger \
jaegertracing/all-in-one:1
```

By default, Synapse will publish traces to Jaeger on localhost.
If Jaeger is hosted elsewhere, point Synapse to the correct host by setting
`opentracing.jaeger_config.local_agent.reporting_host` [in the Synapse configuration](usage/configuration/config_documentation.md#opentracing-1)
or by setting the `JAEGER_AGENT_HOST` environment variable to the desired address.

Latest documentation is probably at
https://www.jaegertracing.io/docs/latest/getting-started.

Expand Down
Loading