All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shubhendu Tripathi <shtripat@redhat.com>
To: Wido den Hollander <wido@42on.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Feeding pool utilization data to time series for trending
Date: Tue, 20 Dec 2016 15:47:04 +0530	[thread overview]
Message-ID: <a9d3de3f-ba6f-3baf-5772-08765a502414@redhat.com> (raw)
In-Reply-To: <640241856.4849.1482224383452@ox.pcextreme.nl>

On 12/20/2016 02:29 PM, Wido den Hollander wrote:
>> Op 20 december 2016 om 5:19 schreef Shubhendu Tripathi <shtripat@redhat.com>:
>>
>>
>> Hi Team,
>>
>> Our team is currently working on project named "tendrl" [1][2].
>> Tendrl is a management platform for software defined storage system like
>> Ceph, Gluster etc.
>>
>> As part of tendrl we are integrating with collectd to collect
>> performance data and we maintain the time series data in graphite.
>>
>> I have a question at this juncture regarding pool utilization data.
>> As our thought process goes, we think of using output from command "ceph
>> df" and parse it to figure out pool utilization data and push it to
>> graphite using collectd.
>> The question here is what is/would be performance impact of running
>> "ceph df" command on ceph nodes. We should be running this command only
>> on mon nodes I feel.
>>
> Correct, that data comes from the MONs and is not that heavy.
>
>> Wanted to verify with the team here if this thought process is in right
>> direction and if so what ideally should be frequency of running the
>> command "ceph df" from collectd.
>>
> Running the command means forking a process every time and also going through the whole cephx authentication and client <> MON process.
>
>> This is just from our point of view and we are open to any other
>> foolproof solution (if any).
> The best would be to keep a open connection to a MON and run the 'df' command directly on the MONs in a loop.
>
> I wrote something like that in Python a while ago for 'ceph status': https://gist.github.com/wido/ac53ae01d661dd57f4a8
>
> cmd = {"prefix":"status", "format":"json"}
>
> If you change that to:
>
> cmd = {"prefix":"df", "format":"json"}
>
> You ask the MON for 'df' and get back a JSON. Run that in a loop where you sleep every 1 or 5 seconds and you should have very real-time information.

Thanks Wido. This is for sure a good suggestion.
I would try to incorporate this and test once.

Regards,
Shubhendu

>
> Wido
>
>> Kindly guide us.
>>
>> Regards,
>> Shubhendu Tripathi
>>
>> [1] http://tendrl.org/
>> [2] https://github.com/tendrl/
>> --
>> 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:[~2016-12-20 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0dafd5ff-1ed6-cb05-05d3-dff3afb43c44@redhat.com>
     [not found] ` <c0ef7893-2bd2-d11f-b008-db566145ce84@redhat.com>
2016-12-20  4:19   ` Feeding pool utilization data to time series for trending Shubhendu Tripathi
2016-12-20  8:59     ` Wido den Hollander
2016-12-20 10:17       ` Shubhendu Tripathi [this message]
2016-12-20 10:22     ` John Spray
2016-12-20 11:43     ` Ruben Kerkhof

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=a9d3de3f-ba6f-3baf-5772-08765a502414@redhat.com \
    --to=shtripat@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=wido@42on.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.