From: Lars Marowsky-Bree <lmb@suse.com>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: SMART disk monitoring
Date: Mon, 13 Nov 2017 12:00:21 +0100 [thread overview]
Message-ID: <20171113110021.374fj4y6elmofrx2@suse.com> (raw)
In-Reply-To: <CALe9h7eU_UiU93AUgJ4819Q2So5V=Nabjmz7ViHcJioXngknQA@mail.gmail.com>
On 2017-11-13T10:46:25, John Spray <jspray@redhat.com> wrote:
> At the risk of stretching the analogy to breaking point, when we build
> something "batteries included", it doesn't mean someone can't also
> plug it into a mains power supply :-)
Plugging something designed to take 2x AAA cells into a mains power
supply is usually considered a bad idea, though ;-)
> My attitude to prometheus is that we should use it (a lot! I'm a total
> fan boy) but that it isn't an exclusive relationship: plug prometheus
> into Ceph and you get the histories of things, but without prometheus
> you should still be able to see all the latest values.
That makes sense, of course. Prometheus scrapes values from various
sources, and if it could scrape data directly off the ceph-osd
processes, why not.
> In that context, I would wonder if it would be better to initially do
> the SMART work with just latest values (for just latest vals we could
> persist these in config keys), and any history-based failure
> prediction would perhaps depend on the user having a prometheus server
> to store the history?
That isn't a bad idea, but would you really want to persist this in a
(potentially rather large) map? That'd involve relaying them to the MONs
or mgr.
Wouldn't it make more sense for something that wants to look at this
data to contact the relevant daemon? It exposing the data also in the
Prometheus exporter format would be useful (so they can directly be
ingested), of course.
This would allow a platform like kubernetes and Prometheus combined to
take care of the automatic service discovery eventually too, and would
even work well for micro-server deployments.
If going down this route though, might want to directly link SMART
libraries into ceph-osd so the daemon doesn't need to call out to
smartctl.
Regards,
Lars
--
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
next prev parent reply other threads:[~2017-11-13 11:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 17:58 SMART disk monitoring Sage Weil
2017-11-10 23:45 ` Ali Maredia
2017-11-11 3:36 ` Yaarit Hatuka
2017-11-12 17:16 ` Lars Marowsky-Bree
2017-11-12 20:16 ` Sage Weil
2017-11-13 10:46 ` John Spray
2017-11-13 11:00 ` Lars Marowsky-Bree [this message]
2017-11-13 13:28 ` Sage Weil
2017-11-13 13:31 ` Sage Weil
2017-11-13 11:53 ` Piotr Dałek
2017-11-14 4:09 ` Ric Wheeler
2017-11-14 8:28 ` Piotr Dałek
2017-11-14 14:19 ` Sage Weil
2017-11-15 0:09 ` Huang Zhiteng
2018-01-03 16:37 ` Sage Weil
2018-01-03 17:28 ` Kyle Bader
2018-01-03 20:36 ` Jan Fajerski
2018-01-03 22:44 ` Lars Marowsky-Bree
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=20171113110021.374fj4y6elmofrx2@suse.com \
--to=lmb@suse.com \
--cc=ceph-devel@vger.kernel.org \
/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.