Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

all_scheduling_group should use both read and write and be per cluster #1872

Closed
amnonh opened this issue Jan 31, 2023 · 1 comment
Closed

all_scheduling_group should use both read and write and be per cluster #1872

amnonh opened this issue Jan 31, 2023 · 1 comment
Labels
bug Something isn't working right
Milestone
Monitoring 4.2

Comments

@amnonh
Copy link
Collaborator

amnonh commented Jan 31, 2023

all_scheduling_group is only looks at writes so it filterout latencies with read but no writes.
It also should be per cluster so dashboards for multiple clusters will work as expected
@amnonh amnonh added the bug Something isn't working right label Jan 31, 2023
@amnonh amnonh mentioned this issue Jan 31, 2023
Merged
@amnonh amnonh added this to the Monitoring 4.3 milestone Jan 31, 2023
@amnonh
Copy link
Collaborator Author

amnonh commented Jan 31, 2023

Fixed by #1870

@amnonh amnonh closed this as completed Jan 31, 2023
@amnonh amnonh modified the milestones: Monitoring 4.3, Monitoring 4.2 Feb 6, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
bug Something isn't working right
Projects
None yet
Milestone
Monitoring 4.2
Development

No branches or pull requests
1 participant
@amnonh