Skip to content

[BUGFIX] pyroscope: include time range in lookup query keys - #849

Merged
Gladorme merged 1 commit into
perses:mainfrom
luweglarz:fix/pyroscope-label-query-keys-time-range
Oct 2, 2026
Merged

Gladorme merged 1 commit into
perses:mainfrom
luweglarz:fix/pyroscope-label-query-keys-time-range

Conversation

@luweglarz

Copy link
Copy Markdown
Contributor

Description

The Pyroscope lookup hooks (useLabelNames, useLabelValues, useProfileTypes, useServices) send start/end in the request, but the time range was not part of their React Query queryKey. When the dashboard time range changed, the cached result for the old range was reused, so the dropdowns could show stale or missing labels, services, and profile types.

Changes

  • Add start and end to the query key of all four hooks, so a new time range triggers a new lookup.

Follow-up to #835 (comment)

Screenshots

Checklist

  • Pull request has a descriptive title and context useful to a reviewer.
  • Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
    following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
  • All commits have DCO signoffs.

Signed-off-by: luweglarz <lucas.weglarz@amadeus.com>
@luweglarz
luweglarz requested a review from a team as a code owner October 1, 2026 09:13
@luweglarz
luweglarz requested review from jgbernalp and removed request for a team October 1, 2026 09:13
@Gladorme
Gladorme added this pull request to the merge queue Oct 2, 2026
Merged via the queue into perses:main with commit 2a87215 Oct 2, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants