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

OTel export failure: DNS resolution failed when using an http:// exporter endpoint #60

Open
giannello opened this issue Aug 5, 2024 · 0 comments

Comments

@giannello
Copy link

Describe the bug

The exporter endpoint is not correctly resolved when specified with a leading http://

To reproduce

otel_exporter {
    endpoint http://collector.collector.svc.cluster.local.:4317;
}

The logs will contain

OTel export failure: DNS resolution failed for http://collector.collector.svc.cluster.local.:4317: C-ares status is not ARES_SUCCESS qtype=A name=http://collector.collector.svc.cluster.local.:4317 is_balancer=0: Domain name not found

Expected behavior

Nginx sends traces to the OTEL collector

Your environment

nginx/1.27.0

Additional context

According to the OTEL documentation, the http prefix must be supported also for GRPC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant