All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: sjust@redhat.com, Sreenath BH <bhsreenath@gmail.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Slow OSD detection
Date: Fri, 21 Nov 2014 15:07:47 -0600	[thread overview]
Message-ID: <546FA9A3.8090908@redhat.com> (raw)
In-Reply-To: <CA+4uBUbxsK-TwWvWjr_ynVOjsRic5YD+Qm2CbzwPxgyTWMs7kg@mail.gmail.com>

It'd be nice if something like slow OSD detection could exist outside of 
calamari and itself by an event that we record in the logs and make 
available via the admin socket (so that calamari could pick it up). 
That way folks could get it into logstash and other system monitoring 
tools (say PCP/Nagios/etc).

Mark

On 11/21/2014 02:58 PM, Samuel Just wrote:
> It's still an open item.  #ceph-devel would be a good place to bounce
> ideas.  Through the admin_socket and perf_counter machinery, the osds
> already expose a bunch of information about queue length, latency,
> etc.  This might actually fit well in calamari, which already gathers
> a bunch of those stats.
> -Sam
>
> On Thu, Nov 20, 2014 at 9:00 PM, Sreenath BH <bhsreenath@gmail.com> wrote:
>> Hi All
>>
>> Slow OSD detection is mentioned as one of the projects ideas in
>> https://wiki.ceph.com/Development/Project_Ideas
>>
>> I am interested in implementing this. Is this still an open item?
>>
>> thanks,
>> Sreenath
>> --
>> 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
> --
> 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
>


  reply	other threads:[~2014-11-21 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  5:00 Slow OSD detection Sreenath BH
2014-11-21 20:58 ` Samuel Just
2014-11-21 21:07   ` Mark Nelson [this message]
2014-11-21 21:29     ` Samuel Just
2014-11-24  7:18       ` Sreenath BH
2015-01-13 12:52         ` Sreenath BH

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=546FA9A3.8090908@redhat.com \
    --to=mark.nelson@inktank.com \
    --cc=bhsreenath@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sjust@redhat.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.