From: Wido den Hollander <wido@widodh.nl>
To: Ugis <ugis22@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: status monitoring options for ceph cluster
Date: Wed, 02 Jan 2013 16:08:41 +0100 [thread overview]
Message-ID: <50E44D79.6070809@widodh.nl> (raw)
In-Reply-To: <CAE63xUOt5dpKPnYXN-nbJHPhPdAW2yH3ERDkwE7QO3TaVLFg4Q@mail.gmail.com>
On 01/02/2013 04:05 PM, Ugis wrote:
> Hi all,
>
> I am planning to set up monitoring of ceph cluster relying on output
> of commands:
>
> #ceph health
> #ceph -s
>
> The need is to retrieve certain values, for example %degraded;
> proportion "X GB / Y GB avail" to calculate available space%. I plan
> to graph those values via zabbix and set up triggers for certain
> tresholds.
> May be somebody already has written shell parser for getting values
> from output of these commands?
>
> Probably this ir wider question - what is the intended approach for
> ceph cluster monitoring? What do you guys use?
You might want to take a look at: http://tracker.newdream.net/issues/685
In version 0.35 a json output was added. I've never tried it before, but
you might want to look at that.
A blogpost was also recently added:
http://ceph.com/community/monitoring-a-ceph-cluster/
Wido
>
> BR,
> Ugis
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-01-02 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 15:05 status monitoring options for ceph cluster Ugis
2013-01-02 15:08 ` Wido den Hollander [this message]
2013-01-02 15:58 ` Joao Eduardo Luis
2013-01-02 16:34 ` Dennis Jacobfeuerborn
2013-01-02 23:02 ` Dan Mick
2013-01-02 23:05 ` Dan Mick
2013-01-03 10:26 ` Wido den Hollander
2013-01-03 16:51 ` Sage Weil
2013-01-03 0:00 ` Paul Pettigrew
2013-01-03 9:13 ` Ugis
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=50E44D79.6070809@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=ugis22@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.