You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When Query Rejection configured with only properties that is not applicable for the API, then it rejects all the metadata queries. For example, dashboard_uid and panel_id headers are not provided for Metadata queries, and if query rejection configured to only those two fields, then it will reject all the Metadata queries for that tenant.
To Reproduce
Steps to reproduce the behavior:
Configure Query rejection with below config
Expected behavior
It should only reject queries that is matching the query_attributes. It shouldn't be rejecting metadata queries because they don't match (no dashboard_uid or panel_id header for them)
Environment:
Any
Additional Context
The text was updated successfully, but these errors were encountered:
Describe the bug
When Query Rejection configured with only properties that is not applicable for the API, then it rejects all the metadata queries. For example, dashboard_uid and panel_id headers are not provided for Metadata queries, and if query rejection configured to only those two fields, then it will reject all the Metadata queries for that tenant.
To Reproduce
Steps to reproduce the behavior:
Configure Query rejection with below config
Expected behavior
It should only reject queries that is matching the query_attributes. It shouldn't be rejecting metadata queries because they don't match (no dashboard_uid or panel_id header for them)
Environment:
Additional Context
The text was updated successfully, but these errors were encountered: