Re: status monitoring options for ceph cluster

[Dan Mick <dan.mick@inktank.com>]

(and of course it makes sense to build those on libraries that could
serve other access methods)

On 01/02/2013 03:02 PM, Dan Mick wrote:
> There are plans being discussed for RESTful interfaces for configuration
> and monitoring; no timetable yet but it's definitely on our radar, and
> we'll discuss design etc. here when it starts happening; anyone wanting
> to participate is of course welcome.
>
> On 01/02/2013 08:34 AM, Dennis Jacobfeuerborn wrote:
>> On 01/02/2013 04:58 PM, Joao Eduardo Luis wrote:
>>> On 01/02/2013 03:08 PM, Wido den Hollander wrote:
>>>> 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.
>>>
>>> Currently, the only command that will output useful json for this
>>> kind of
>>> thing is 'ceph report'. I am finishing up on a patch to add json output
>>> capabilities to 'ceph health' and 'ceph status' though, but wasn't
>>> aiming
>>> at doing it with such level of detail -- basically, just output the same
>>> info as their plain counterparts, but using json instead.
>>
>> I'm interested in this topic as well. What is also needed is a way to
>> query
>> the state of the individual daemons on each machine in the cluster.
>>
>> Regards,
>>    Dennis
>>
>> --
>> 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
>>