-
Notifications
You must be signed in to change notification settings - Fork 40
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
Improve etcd dashboard #9
Conversation
@jaredoconnell Nice! @rsevilla87 PTAL |
'process_resident_memory_bytes{pod=~"$pod",job=~"$cluster"}', | ||
format='table', | ||
instant=true, | ||
'histogram_quantile(0.99, rate(etcd_network_peer_round_trip_time_seconds_bucket[5m]))', |
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.
Peer to peer network latency is a great addition @jaredoconnell.
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
Nice work @jaredoconnell. |
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.
Awesome @jaredoconnell , LGTM!
This addresses issue #2
It uses the prometheus calls from https://github.com/tkashem/dittybopper/blob/dashboard/dashboards/etcd-overview.json as requested in the issue.
I positioned the data in a way that seemed logical, though I can easily move them.
Here are the pictures from a test aws cluster: