search

kubernetes / ingress-nginx

Ingress NGINX Controller for Kubernetes
https://kubernetes.github.io/ingress-nginx/
Apache License 2.0
17.5k stars 8.26k forks source link

OTLP GRPC Exporter failing to connect, preventing trace data export #11991

Open kadhamecha-conga opened 1 month ago

kadhamecha-conga commented 1 month ago

hi,

GRPC Exporter is failing to establish a connection with the configured endpoint, resulting in the inability to export trace data.

[Error] File: /tmp/build/opentelemetry-cpp/exporters/otlp/src/otlp_grpc_exporter.cc:66 [OTLP TRACE GRPC Exporter] Export() failed with status_code: "UNAVAILABLE" error_message: "failed to connect to all addresses; last error: UNKNOWN: ipv4:x.x.x.x:443: connection attempt timed out before receiving SETTINGS frame"

helm.sh/chart : ingress-nginx-4.11.3 app.kubernetes.io/version : 1.11.2

nginx otel config :

allow-snippet-annotations: 'true' client-header-buffer-size: 128k enable-opentelemetry: 'true' hide-headers: server hsts: 'true' hsts-include-subdomains: 'true' hsts-max-age: '31536000' large-client-header-buffers: 8 128k load-balance: ewma opentelemetry-operation-name: HTTP $request_method $service_name $uri opentelemetry-trust-incoming-span: 'true' otel-max-export-batch-size: '512' otel-max-queuesize: '2048' otel-sampler: AlwaysOn otel-sampler-parent-based: 'true' otel-sampler-ratio: '1.0' otel-schedule-delay-millis: '5000' otel-service-name: nginx-ingress otlp-collector-host: "signals.test.com" otlp-collector-port: '443' proxy-body-size: 100m proxy-buffer-size: 128k proxy-buffering: 'on' proxy-buffers-number: '4' proxy-connect-timeout: '120' proxy-headers-hash-bucket-size: '256' proxy-headers-hash-max-size: '1024' proxy-read-timeout: '3600' proxy-send-timeout: '3600' server-names-hash-bucket-size: '256' server-names-hash-max-size: '1024' use-forwarded-headers: 'true' use-http2: 'true'

thanks,

k8s-ci-robot commented 1 month ago

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
longwuyuan commented 1 month ago

/assign @esigo

kadhamecha-conga commented 1 month ago

hi @esigo , is grpc with TLS supported with nginx opentelemetry ?

bansalrajat commented 3 weeks ago

same error