Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not possible to set Jaeger tracing address through Grafana config #25563

Closed
marefr opened this issue Jun 12, 2020 · 0 comments · Fixed by #25768
Closed

Not possible to set Jaeger tracing address through Grafana config #25563

marefr opened this issue Jun 12, 2020 · 0 comments · Fixed by #25768
Assignees
Labels
area/instrumentation instrumentation for Grafanas codebase. type/bug
Milestone

Comments

@marefr
Copy link
Member

marefr commented Jun 12, 2020

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
@marefr marefr added type/bug area/instrumentation instrumentation for Grafanas codebase. labels Jun 12, 2020
@marefr marefr self-assigned this Jun 23, 2020
@marefr marefr removed this from Bugs in Backend Platform Backlog Jun 23, 2020
@marefr marefr added this to In progress in Backend Platform Squad Jun 23, 2020
@marefr marefr added this to the 7.1 milestone Jun 23, 2020
@marefr marefr moved this from In progress to Under review in Backend Platform Squad Jun 23, 2020
Backend Platform Squad automation moved this from Under review to Done Jun 23, 2020
marefr added a commit that referenced this issue Jun 23, 2020
…onfig (#25768)

Upgrades jaeger-client-go to v2.24.0 to resolve problem with setting Jaeger tracing 
address through Grafana config.

Fixes #25563
aknuds1 pushed a commit that referenced this issue Jun 30, 2020
…onfig (#25768)

Upgrades jaeger-client-go to v2.24.0 to resolve problem with setting Jaeger tracing 
address through Grafana config.

Fixes #25563
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/instrumentation instrumentation for Grafanas codebase. type/bug
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant