You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Received error when enabled Jaeger tracing using Grafana configuration:
EROR[06-12|13:08:08] error when flushing the buffer: write udp 127.0.0.1:54672->127.0.0.1:6831: write: connection refused logger=jaeger
What you expected to happen:
That Jaeger should use the address configured in Grafana and not log an error and by that function as expected.
How to reproduce it (as minimally and precisely as possible):
Changed Grafana configuration to enable Jaeger tracing:
[tracing.jaeger]
# jaeger destination (ex localhost:6831)
address = 172.21.0.4:6831
Anything else we need to know?:
If I set the environment variable export JAEGER_AGENT_HOST=172.21.0.4 before starting Grafana Jaeger works as expected. Seems like the problem is that environment variable override in Jaeger client library overrides agent host or port to the default if they're not provided through environment variables. There's a fix merged, but still no official version tagged including those changes, ref jaegertracing/jaeger-client-go#513.
Environment:
Grafana version: master / 7.0.3
The text was updated successfully, but these errors were encountered:
What happened:
Received error when enabled Jaeger tracing using Grafana configuration:
What you expected to happen:
That Jaeger should use the address configured in Grafana and not log an error and by that function as expected.
How to reproduce it (as minimally and precisely as possible):
Changed Grafana configuration to enable Jaeger tracing:
Anything else we need to know?:
If I set the environment variable
export JAEGER_AGENT_HOST=172.21.0.4
before starting Grafana Jaeger works as expected. Seems like the problem is that environment variable override in Jaeger client library overrides agent host or port to the default if they're not provided through environment variables. There's a fix merged, but still no official version tagged including those changes, ref jaegertracing/jaeger-client-go#513.Environment:
The text was updated successfully, but these errors were encountered: