>(c) makes the nervous. You shouldn't need to consume daemonperf output; >the 'ceph daemon <name> perf dump' provides the same (and more) data in >json form. Yes, we do use "perf dump" but borrow the code pieces from daemonperf to parse the result, you may need to sub, max, or calc interval average, based on the counter's type. Prometheus is a MUST for such use case as it can do histogram and enable us to show percentile (like 95% commit latency) on dashboard, it is the only way to read 1000+ osd's metrics. 2017-05-19 20:22 GMT+08:00 Dan van der Ster <dan@xxxxxxxxxxxxxx>: > On Fri, May 19, 2017 at 2:18 PM, Sage Weil <sage@xxxxxxxxxxxx> wrote: >> I'm also curious how the grafana dashboards are built (I haven't used >> Grafana before). Is this the sort of thing where the dashboards can be >> developed and managed in source control? It would be great to have a >> bunch of pre-built and collaboratively developed Ceph dashboards! > > A grafana dashboard is described by a json file, which can exported > and shared, e.g. at https://grafana.com/dashboards > > -- dan -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
