CEPH filesystem development
 help / color / mirror / Atom feed
From: Lenz Grimmer <lgrimmer-IBi9RG/b67k@public.gmane.org>
Cc: ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ceph-users <ceph-users-Qp0mS5GaXlQ@public.gmane.org>
Subject: Re: Show and Tell: Grafana cluster dashboard
Date: Mon, 4 Jun 2018 12:56:25 +0200	[thread overview]
Message-ID: <e154f1d5-6165-7116-e999-aabd2caa6292@suse.com> (raw)
In-Reply-To: <b461c88c-9789-9a17-e67d-a4913c15466f-IBi9RG/b67k@public.gmane.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1120 bytes --]

On 05/08/2018 07:21 AM, Kai Wagner wrote:

> Looks very good. Is it anyhow possible to display the reason why a
> cluster is in an error or warning state? Thinking about the output from
> ceph -s if this could by shown in case there's a failure. I think this
> will not be provided by default but wondering if it's possible to add.

Sorry for the late reply. We actually discussed this aspect during one
of the calls we had when discussing the Grafana dashboard integration
into the Ceph Manager Dashboard. Such kind of state information is
somewhat difficult to track and visualize using Prometheus/Grafana (or
any other TSDB, FWIW), as you can't store the actual reasons for why the
cluster is in HEALTH_WARN or HEALTH_ERR, for example.

We are therefore considering displaying this information in the form of
"native" widgets on the Manager Dashboard, and using the Grafana
dashboards for visualizing the other more suitable performance metrics.

Lenz

-- 
SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany)
GF:Felix Imendörffer,Jane Smithard,Graham Norton,HRB 21284 (AG Nürnberg)


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 178 bytes --]

_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

  parent reply	other threads:[~2018-06-04 10:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <"H000007100119c41.1525680369.sx.f1-outsourcing.eu*"@MHS>
2018-05-07 14:53 ` Show and Tell: Grafana cluster dashboard Reed Dier
     [not found]   ` <6A5C4896-0EFA-4F2E-8963-2DFA7D78C48D-uHprvc9sRvVBDgjK7y7TUQ@public.gmane.org>
2018-05-08  5:21     ` Kai Wagner
     [not found]       ` <b461c88c-9789-9a17-e67d-a4913c15466f-IBi9RG/b67k@public.gmane.org>
2018-06-04 10:56         ` Lenz Grimmer [this message]
2018-05-07 12:05 Kurt Bauer
     [not found] ` <328d036f-87be-c85f-1d48-605edb3a0c63-4JhlDu4IDl0juwv8T7myQQ@public.gmane.org>
2018-05-07 12:21   ` Jan Fajerski
2018-05-07 12:45   ` Kurt Bauer
     [not found]     ` <007c00b9-34c9-2871-6bc9-d9aa7bf5dede-4JhlDu4IDl0juwv8T7myQQ@public.gmane.org>
2018-05-07 13:12       ` Jan Fajerski
  -- strict thread matches above, loose matches on Subject: below --
2018-05-07 10:32 Jan Fajerski
2018-05-07  8:06 Marc Roos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e154f1d5-6165-7116-e999-aabd2caa6292@suse.com \
    --to=lgrimmer-ibi9rg/b67k@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox