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

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

Open
kadhamecha-conga opened this issue Sep 19, 2024 · 4 comments
Open
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@kadhamecha-conga
Copy link

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,

@kadhamecha-conga kadhamecha-conga added the kind/bug Categorizes issue or PR as related to a bug. label Sep 19, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 19, 2024
@k8s-ci-robot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@longwuyuan
Copy link
Contributor

/assign @esigo

@kadhamecha-conga
Copy link
Author

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

@bansalrajat
Copy link

same error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

5 participants