From: Stefan Priebe <s.priebe@profihost.ag>
To: Gregory Farnum <greg@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Statistics / Nagios
Date: Sun, 25 Nov 2012 20:32:13 +0100 [thread overview]
Message-ID: <50B2723D.5020904@profihost.ag> (raw)
In-Reply-To: <9536A23884D44002B4C59911713210DF@inktank.com>
Hi Greg,
Am 25.11.2012 20:08, schrieb Gregory Farnum:
> On Sunday, November 25, 2012 at 10:26 AM, Stefan Priebe wrote:
>> Hello list,
>>
>> are there any useful statistics for ceph? ceph -s shows just the status
>> but i would like to record something which gives me an idea about the
>> ceph load or usage.
>
> Each daemon has an admin socket which you can use to extract "perfcounters" (performance counters). It's not well-documented at all right now, unfortunately.
> "ceph --admin-daemon /path/to/admin/socket help"
> "ceph --admin-daemon /path/to/admin/socket perfcounters_dump"
>
> "ceph --admin-daemon /path/to/admin/socket perfcounters_schema"
>
> should get you started.
> http://ceph.com/docs/master/radosgw/troubleshooting has some examples of troubleshooting the gateway with them.
thanks! I don't use radosgw. Just ceph-mon and ceph-osd with rbd block
devices.
So i have to query each OSD on their own?
Right now i have
[global]
admin socket=/var/run/ceph.sock
but that gives:
# ceph --admin-daemon /var/run/ceph.sock perfcounters_schema
{}
Greets,
Stefan
next prev parent reply other threads:[~2012-11-25 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 18:26 Statistics / Nagios Stefan Priebe
2012-11-25 19:08 ` Gregory Farnum
2012-11-25 19:32 ` Stefan Priebe [this message]
2012-11-26 21:17 ` Dan Mick
2012-11-26 23:46 ` Gregory Farnum
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=50B2723D.5020904@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.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.