Dashboard updates #90
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changes are as follows; ceph-osd-latency --> ceph-osd-information ceph-rados --> ceph-cluster ceph-frontend --> ceph-pools
Added triggers for OSD node loss and Long OSD response times removed IO Stall trigger - firing to often during scrub
Graphs now aggregate across ceph roles, and provide drill down by role to show network load at each layer.
Renamed to ceph-cluster to better reflect the metrics and data shown on the dashboard
changes include; - support for osd and disk name to provide filters to the graphs - add osd overview row containing - raw capacity panel - host.disk -> disk size table - host.disk -> osd id - shortcut links added to other overview type dashboards
…ance data Summary row shows; - osd count - osd up count - osd's down - disk size summary (pie chart showing what sizes of disk are in the cluster - table of osd to disk size - OSD encryption summary (how many of my OSDs are encrypted?) - OSD type status (how many OSDs are filestore vs bluestore Panel includes an OSD id which is used as a filter for the filestore performance row The performance row now shows average OSD performance for a single OSD or all OSDs. This can then be used for side-by-side comparison with OSD performance across the cluster at the 95%ile.
OSD capacity by Host table added to the summary row, showing capacity by host Performance data split into two rows, allowing each one to be hidden independently
In addition to the link updates - scrub state reflects both scrub and deep-scrub status - the scrub panel no longer turns to "warn" when scrub is active - it's a natural feature of the cluster and not a problem! However, it will turn red, if scrub or deep-scrub is disabled - disk util panel changed to a graph and switched to average and 95%ile (95%ile on a busy cluster just shows too much variance) - OSDs panel now links to the ceph-osd-information dashboard
This was referenced Aug 2, 2017
zmc
requested changes
Aug 2, 2017
tools/prettyJSON.py
Outdated
| @@ -0,0 +1,77 @@ | |||
| #!/usr/bin/env python2 | |||
There was a problem hiding this comment.
We don't actually need this; one can simply cat foo.json | python -m 'json.tool'
There was a problem hiding this comment.
Agree. The code I added ; validates the file is a standard name, checks the json itself is valid, and outputs the results to a _new.json version of the file. I'll drop the commit.
pcuzner
force-pushed
the
dashboard-updates
branch
from
41bd829
to
72af517
Compare
|
@zmc prettyJSON.py removed |
Initial commit did not use the right metric - missed due to low load, more obvious on larger systems!
In a 600+ OSD environment the charts were based on averageSeries which was taking a long time. This has now been changed, so the comparison chart only shows current values for a given OSD for comparison
zmc
approved these changes
Aug 4, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
dashboard fixes and enhancements moving towards a 1.0, which includes an update to the default alert triggers.
When deploying consider the following;
In addition to the updates the dashboards are stored in formatted json now to help readability, and a tools/prettyJSON.py added to create the formatted json from the exported (api) output of Grafana