This is a known issue in the loki-logger plugin: when the plugin is used as a global rule or shares the same configuration table (conf) across requests, the log_labels table is mutated in-place for each request. This can cause label values from one request to leak into logs for other requests, especially in multi-worker or high-concurrency environments. That's why you see inconsistent or "cross-route" values in your logs. The log_format fields are built per request and are less likely to leak, but if the request context (ctx) is not properly isolated, inconsistencies can still occur.

To reduce the risk, configure the plugin per route or service instead of globally. Avoid sharing mutable config tables across requests. Keep an eye on future APISIX releases for a fix to this in-place mutation issue. More details and discussion can be found in this GitHub issue and the loki-logger source code.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

@renshunhang Hello, could you please provide the minimal reproduction steps so I can quickly locate the problem?