Skip to content

Query Rejection for Metadata Queries Bug #6143

Closed
@erlan-z

Description

@erlan-z

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

    query_rejection:
      enabled: true
      query_attributes:
        - dashboard_uid: "dash123"
          panel_id: "panel123"
  1. Start Cortex (SHA or version)
  2. Perform Operations(Query metadata API)

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions