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

Commit 3bcb6a0

Browse files
authored
Mention how to redirect the Jaeger traces to a specific Jaeger instance (#16531)
1 parent 3a0aa6f commit 3bcb6a0

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

changelog.d/16531.doc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Add a sentence to the opentracing docs on how you can have jaeger in a different place than synapse.

docs/opentracing.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,11 @@ docker run -d --name jaeger \
5151
jaegertracing/all-in-one:1
5252
```
5353

54+
By default, Synapse will publish traces to Jaeger on localhost.
55+
If Jaeger is hosted elsewhere, point Synapse to the correct host by setting
56+
`opentracing.jaeger_config.local_agent.reporting_host` [in the Synapse configuration](usage/configuration/config_documentation.md#opentracing-1)
57+
or by setting the `JAEGER_AGENT_HOST` environment variable to the desired address.
58+
5459
Latest documentation is probably at
5560
https://www.jaegertracing.io/docs/latest/getting-started.
5661

0 commit comments

Comments
 (0)