On 2018-01-03T21:36:56, Jan Fajerski <jfajerski@xxxxxxxx> wrote:
> We do collect SMART data with the mechanism described above. We use salt to
> setup up a cronjob (though say a systemd timer would also work) that runs
> smartmon.sh > node_exporter/text_collector_dir/file.
> It does not work out of the box, but that is how the node_exporter is meant
> to be extended afaiu.
I could see this being more neatly handled by having a smarter exporter
that pulls data on-demand on scrape, and then manage the intervals
accordingly via that mechanism, but that'd be inefficient with multiple
Prometheus instances scraping (which is a common setup).
I'd prefer if we got JSON directly out of smartctl, of course. But even
ceph-osd would probably only do periodic scrapes for the above
reasons.
Unless you want ceph-osd to take direct action, I'm not sure there's a
need for it to handle this internally.
Also, how would it handle things like devices shared between OSDs, e.g.,
the WAL/journals? That's better handled via an outside scheduler.
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
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
