krakend-ce icon indicating copy to clipboard operation
krakend-ce copied to clipboard

Tracing headers not propagate to backend

Open raafael opened this issue 9 months ago • 0 comments

Environment info:

  • KrakenD version: 2.6.3
  • System info: docker
  • Backend technology: Go

I'm not getting the tracing headers in my backend, in the docs https://www.krakend.io/docs/endpoints/parameter-forwarding/#default-headers-sent-from-krakend-to-backends I understand if we are using tracing in krakend the headers: X-B3-Sampled, X-B3-Spanid and X-B3-Traceid should arrive at backend.

I'm debbuging the headers in a Golang app that krakend call and there isn't any header about tracing. In my krakend configuration file for backend I configure "input_headers" with "*". And I'm using the tracing config from the docs export to jaeger.

"telemetry/opentelemetry": {
    "service_name": "krakend",
    "metric_reporting_period": 1,
    "layers": {
        "global": {
            "report_headers": true
        },
        "proxy": {
            "report_headers": true
        },
        "backend": {
            "metrics": {
                "disable_stage": true
            },
            "traces": {
                "disable_stage": false,
                "round_trip": true,
                "read_payload": true,
                "detailed_connection": true,
                "report_headers": true
            }
        }
    },
    "exporters": {
        "prometheus": [
            {
                "name": "prometheus_exporter",
                "port": 9090,
                "process_metrics": true,
                "go_metrics": true
            }
        ],
        "otlp": [
            {
                "name": "local_jaeger",
                "host": "jaeger",
                "port": 4317,
                "use_http": false,
                "disable_metrics": true
            }
        ]
    }
}

Am I missing something?

raafael avatar May 21 '24 20:05 raafael