Skip to content
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

add hints related graphs #545

Closed
vladzcloudius opened this issue Mar 25, 2019 · 3 comments · Fixed by #835
Closed

add hints related graphs #545

vladzcloudius opened this issue Mar 25, 2019 · 3 comments · Fixed by #835

Comments

@vladzcloudius
Copy link
Contributor

HEAD: dd390a6

Feature requests
Add hints related graphs.
Hints metrics are coordinator metrics however it also makes sense to have them not too far from the replica side metrics because they are correlated with these.

@tzach
Copy link
Contributor

tzach commented Mar 25, 2019

@vladzcloudius please include the relevant metrics names.

@vladzcloudius
Copy link
Contributor Author

@tzach scylla_hints_for_views_manager_* and scylla_hints_manager_*

@amnonh amnonh added the 2.4 label Apr 2, 2019
@tzach tzach added this to the Monitoring 2.4 milestone Apr 2, 2019
@tzach tzach removed 2.4 labels Apr 2, 2019
@amnonh amnonh modified the milestones: Monitoring 2.4, monitoring 2.5 Jun 10, 2019
@amnonh amnonh modified the milestones: monitoring 3.0, monitoring 3.1 Jul 17, 2019
@amnonh amnonh modified the milestones: monitoring 3.1, monitoring 3.2 Dec 24, 2019
@vladzcloudius
Copy link
Contributor Author

@amnonh ping.

I looked at the current dashboards state in the master: it seems to make sense to start with adding the scylla_hints_manager_writes and scylla_hints_manager_sent graphs in the Coordinator group on the Detailed dashboard and adding scylla_hints_for_views_manager_writes and scylla_hints_for_views_manager_sent graphs in the View section.

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 a pull request may close this issue.

3 participants