apollographql / router

A configurable, high-performance routing runtime for Apollo Federation 🚀
https://www.apollographql.com/docs/router/
Other
807 stars 272 forks source link

After update to newest version of Apollo otlp tracing export timeouts #4564

Closed voslartomas closed 7 months ago

voslartomas commented 8 months ago

Describe the bug

We used to have this configuration

telemetry:
  tracing:
    trace_config:
      service_name: "..."
      service_namespace: "..."
      parent_based_sampler: true
    propagation:
      baggage: true
    otlp:
      endpoint: https://api.honeycomb.io
      grpc:
        metadata:
          x-honeycomb-team:
            - ${env.apiKey}
          x-honeycomb-dataset:
            - ${env.HONEYCOMB_DATASET}
      protocol: grpc

No had to switch to this after recent update.

telemetry:
  exporters:
    tracing:
      common:
        service_name: "..."
        service_namespace: "..."
        parent_based_sampler: true
      propagation:
        baggage: true
      otlp:
        enabled: true
        endpoint: api.honeycomb.io
        protocol: grpc
        grpc:
          metadata:
            x-honeycomb-team:
              - ${env.apiKey}
            x-honeycomb-dataset:
              - ${env.HONEYCOMB_DATASET}
      experimental_response_trace_id:
        enabled: true # default: false
        header_name: "trace-id"

But having this error in logs, does not say much though. Tried different options with endpoint like, api.honeycomb.io:443 etc, but nothing works.

{"timestamp":"2024-01-30T12:22:05.254400512Z","level":"ERROR","message":"OpenTelemetry trace error occurred: Exporting timed out after 30 seconds","target":"apollo_router::plugins::telemetry","resource":{"service.name":"unknown_service:router","process.executable.name":"router","service.version":"1.38.0"}}
voslartomas commented 7 months ago

We still cannot send traces directly to honeycomb for some reason, even with same configuration as before, but we are able to send it to our otlp collector, so closing.