Describe the bug
extra_filters works perfectly when defined in VMUser (automatically injected by vmauth / auth layer) or when manually passed as a query parameter on native LogsQL endpoints. However, it is completely ignored when using the Jaeger Query API and Tempo API compatibility endpoints.
This prevents proper data separation for users accessing traces via Jaeger UI, Grafana Jaeger or Tempo datasources, or any other tool that uses these APIs.
To Reproduce
You can reproduce it by injecting &extra_filters=... on both native LogsQL and Jaeger/Tempo API endpoints.
Please let me know if you need clear steps to reproduce the issue.
Version
v0.9.2
Logs
No response
Screenshots
No response
Used command-line flags
No response
Additional information
No response
Describe the bug
extra_filtersworks perfectly when defined in VMUser (automatically injected by vmauth / auth layer) or when manually passed as a query parameter on native LogsQL endpoints. However, it is completely ignored when using the Jaeger Query API and Tempo API compatibility endpoints.This prevents proper data separation for users accessing traces via Jaeger UI, Grafana Jaeger or Tempo datasources, or any other tool that uses these APIs.
To Reproduce
You can reproduce it by injecting
&extra_filters=...on both native LogsQL and Jaeger/Tempo API endpoints.Please let me know if you need clear steps to reproduce the issue.
Version
v0.9.2
Logs
No response
Screenshots
No response
Used command-line flags
No response
Additional information
No response