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

Unable to export to Jaeger from OTEL collector #1699

Closed
shrutich91 opened this issue Oct 19, 2022 · 2 comments
Closed

Unable to export to Jaeger from OTEL collector #1699

shrutich91 opened this issue Oct 19, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@shrutich91
Copy link

Describe your environment
I am using the following docker compose

Jaeger Docker:
docker run -d --name jaeger-all-in-one -p 16686:16686 -p 14250:14250 -p 14268:14268 jaegertracing/all-in-one

OTEL Collector Docker:
docker run --rm -it -p 4317:4317 -p 4318:4318 -v $(pwd)/examples/otlp:/cfg otel/opentelemetry-collector:0.59.0 --config=/cfg/opentelemetry-collector-config/config.dev.yaml

OTEL Collector Config

exporters:
jaeger:
endpoint: jaeger:14250
tls:
insecure: true
logging:
loglevel: DEBUG
receivers:
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
http:
endpoint: 0.0.0.0:4318
service:
pipelines:
traces:
receivers:
- otlp
exporters: [logging, jaeger]
logs:
receivers:
- otlp
exporters:
- logging
metrics:
receivers:
- otlp
exporters:
- logging

What is the expected behavior?
I want to export traces from collector to jaeger but getting an error

What is the actual behavior?
kind": "exporter", "data_type": "traces", "name": "jaeger", "state": "CONNECTING"}
2022-10-19T05:55:59.597Z warn zapgrpc/zapgrpc.go:191 [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
"Addr": "jaeger:14250",
"ServerName": "jaeger:14250",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}. Err: connection error: desc = "transport: Error while dialing dial tcp: lookup jaeger on 192.168.65.5:53: read udp 172.17.0.2:43000->192.168.65.5:53: i/o timeout" {"grpc_log": true}
2022-10-19T05:56:00.597Z info jaegerexporter@v0.59.0/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "data_type": "traces", "name": "jaeger", "state": "TRANSIENT_FAILURE"}

@shrutich91 shrutich91 added the bug Something isn't working label Oct 19, 2022
@shrutich91 shrutich91 changed the title Unable to export to Jaeger from OTEL collector: Unable to export to Jaeger from OTEL collector using C++: Oct 19, 2022
@shrutich91 shrutich91 changed the title Unable to export to Jaeger from OTEL collector using C++: Unable to export to Jaeger from OTEL collector Oct 19, 2022
@marcalff
Copy link
Member

This issue seems related to the OTEL collector itself.

Please file collector issues against the collector repository, not against opentelemetry-cpp.
https://github.com/open-telemetry/opentelemetry-collector

@marcalff
Copy link
Member

Opened in collector as:
open-telemetry/opentelemetry-collector#6356

Closing this issue.

@marcalff marcalff closed this as not planned Won't fix, can't repro, duplicate, stale Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants