rape it, but would be very
> lightweight.
> Zabbix can be used also, Data can be pushed for example by zabbix_sender:
> https://www.zabbix.com/documentation/2.4/manpages/zabbix_sender
> Wdyt?
My thinking currently is to write something from scratch. Basically
system monitoring is ab
One lightweight soultion on the client would be to provide a
prometheus exporter, implementing the spec here:
https://prometheus.io/docs/instrumenting/exposition_formats/
That would need a prometheus server to scrape it, but would be very lightweight.
Zabbix can be used also, Data can be pushed for
> I was looking to deploy Nagios on our servers, but I am discouraged by
> its architecture. I would like something minimalistic that can run
> anywhere (including small routers).
I have been looking for minimalistic monitoring systems too and it would
be great to have one written in Guile. I can
On Sun, Dec 29, 2019 at 09:05:40PM +0100, Nicolò Balzarotti wrote:
> I think zabbix should work, but I've never used it. On the surface, it
> seems to have a steep learning curve, but this is just my impression.
The problem with these systems is that they target (complex)
deployments that have pe
cpu usage, temperature from multiple sensors, I was not sure on
how to represent them in a nice way (and I never solved the problem, I
had separate metrics on separate logs).
> System monitoring has a number of important components, but they could
> all be simple and written in guile:
>
>
I was looking to deploy Nagios on our servers, but I am discouraged by
its architecture. I would like something minimalistic that can run
anywhere (including small routers).
System monitoring has a number of important components, but they could
all be simple and written in guile:
1. a (small
