>On 04/23/2016 01:35 PM, Michael Raskin wrote:
>>> That’s what they always say right before they make a 10 person team
>>> work fulltime on a project. ;)
>>
>> Well, they have Bazel… And I have grounds to believe they are not going
>> to use Nix this year.
>
>Bazel's focus seems a little lower,
On 04/23/2016 01:35 PM, Michael Raskin wrote:
>> That’s what they always say right before they make a 10 person team
>> work fulltime on a project. ;)
>
> Well, they have Bazel… And I have grounds to believe they are not going
> to use Nix this year.
Bazel's focus seems a little lower, similar
>> - And I don't suppose I can deny being at Google, no, but this isn't a
>> Google project; I've just ended up using NixOS *everywhere* in my personal
>> life, so now I want monitoring. ;-)
>That’s what they always say right before they make a 10 person team
>work fulltime on a project. ;)
Well,
On 16-04-22 02:08pm, Svein Ove Aas wrote:
> - And I don't suppose I can deny being at Google, no, but this isn't a
> Google project; I've just ended up using NixOS *everywhere* in my personal
> life, so now I want monitoring. ;-)
That’s what they always say right before they make a 10 person team
Thanks for the responses so far!
Let me see...
- I actually agree with Tomas about naming. I know I wrote
"services.monitoring.enable", but I hadn't put a lot of thought into that
sentence; "services.monitoring.prometheus" seems like a better namespace.
- I'd add battery life to the list of
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
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
+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
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
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
10 matches
Mail list logo
