-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mimir ruler reads dashboard query scheduler queue duration breakout improvements #7163
mimir ruler reads dashboard query scheduler queue duration breakout improvements #7163
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is quite right, looks like we'll show data on the standard query path's query-scheduler rather than the ruler query path's query-scheduler.
Also, it might be good to pull these rows shared by both dashboards out to a common place to make it easier to make changes to both in one place.
$.qpsPanel('cortex_query_scheduler_queue_duration_seconds_count{%s}' % $.jobMatcher($._config.job_names.ruler_query_scheduler)) + | ||
$.panelDescription(title, description), | ||
$.panelDescription(title, description) + | ||
$.qpsPanel('cortex_query_scheduler_queue_duration_seconds_count{%s}' % $.jobMatcher($._config.job_names.query_scheduler)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this refer to $._config.job_names.ruler_query_scheduler
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(this also applies to a bunch of changes below - looks like they should all refer to ruler_query_scheduler
, not query_scheduler
)
In a previous PR we did this breakout of one panel into three for the Reads dashboard but forgot to apply the same improvements for Remote Ruler Reads
What this PR does
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.