monlor opened a new issue, #10341: URL: https://github.com/apache/apisix/issues/10341
### Current Behavior When enabling the trace_id nginx variable and configuring the loki-logger plugin with log_labels.trace_id: $opentelemetry_trace_id to set trace_id as a label, it seems to mismatch and sometimes captures trace IDs from other requests. This results in an incorrect association of logs with the corresponding trace IDs. ### Expected Behavior _No response_ ### Error Logs _No response_ ### Steps to Reproduce 1. Run APISIX via the helm. 2. Create a Route using the APISIXROUTE. 3. Configure the loki-logger plugin with log_labels.trace_id: $opentelemetry_trace_id. 4. Observe the trace IDs in the logs, noticing that some of them are mismatched. compare traceparrent and labels ### Environment apisix helm chart 2.3.0 - APISIX version (run `apisix version`): 3.6 - Operating system (run `uname -a`): - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`): - APISIX Dashboard version, if relevant: - Plugin runner version, for issues related to plugin runners: - LuaRocks version, for installation issues (run `luarocks --version`): -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
