That's interesting, however I don't think this should be part of "monitoring" service.
I'm using prometheus daily and I'm following its development and I don't think it's stable enough (for example backend/storage changes quite often), and prometheus is far from 1.0 (stable). I don't agree that something like "monitoring" should be tied to specific software. I personally like debian-way better than redhat-way ("apache2" service instead of "httpd" service which is apache or nginx). So I think I would like to have prometheus service and I would build my system using those blocks. On that level I can use nixops to make a "monitoring" service which consists of many other applications (let's say prometheus + some dashboard + other modules around or I can use totally different software instead, but still it will be monitoring service). 2016-04-21 21:41 GMT+01:00 Layus <layus...@gmail.com>: > I like the idea too. > > It seems to me that distributions really lack metrics collection and > data analysis. > For example, it would be nice to have automatic gathering of the battery > usage (charge/discharge/capacity) and an easy access to compiled > historical data like the capacity loss over the years. > > I know this is far less ambitious than what you describe, but it would > be a great entry point for new users. > If they like it, they may want to gather wore statistics. > > Anyway, I think it makes total sense to have such a feature in NixOS. > > -- Layus. > > On 20/04/16 11:49, Rok Garbas wrote: > > +1 for the initiative. i don't believe personally enabling monitoring > > by default should be the right way to go (since we all use nixos in > > different contexts), but having a commented instructions in generated > > configurations.nix would be the way to go. > > > > it would be nice if systemd monitoring stuff could be used as well: > > https://github.com/garbas/dotfiles/blob/master/nixos/rok.nix#L236 > > above line makes systemd-cgtop showing numbers. > > > > > > > > On Wed, Apr 20, 2016 at 8:44 AM, Alexei Robyn <sha...@shados.net> wrote: > >> Seems interesting. You mention alerts for "System software too old.", > but > >> the only vaguely-universal definition of "too old" I can think of would > be > >> "missing security updates", and that's both debatable and an area where > >> NixOS is currently fairly lacking in infrastructure and tooling. > >> > >> Default collection of metrics beyond what is necessary to provide useful > >> alerts is a bad idea. Alerts have essentially universal usefulness, > >> statistics less so - they're unnecessary for most desktops and small > >> servers. At least until you have issues, so of course it'd be nice if > they > >> were easy to switch on :p. > >> > >> - Alexei > >> > >> > >> On Wed, Apr 20, 2016, at 12:40 AM, Svein Ove Aas wrote: > >> > >> Hi all, > >> > >> People who are not interested in reliability or monitoring can stop > reading > >> now. > >> > >> -- > >> > >> I've written up a "design doc" (statement of intent?) for how we might > do > >> monitoring-by-default. Once I think there is a reasonable level of > consensus > >> about how we should do this, I'll go ahead and implement what's in the > >> document, but I'd like to make sure we're all on the same page first; > >> especially as I want this to be on by default. > >> > >> So I'd like your input. Can you take a look? > >> > >> -- > >> Svein Ove Aas > >> _______________________________________________ > >> nix-dev mailing list > >> nix-dev@lists.science.uu.nl > >> http://lists.science.uu.nl/mailman/listinfo/nix-dev > >> > >> > >> > >> _______________________________________________ > >> nix-dev mailing list > >> nix-dev@lists.science.uu.nl > >> http://lists.science.uu.nl/mailman/listinfo/nix-dev > >> > > > > > > _______________________________________________ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > -- Tomasz Czyż
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev