[deleted]
μMon: Stupid simple monitoring (2022)
61–70 of 110 posts
Re: μMon: Stupid simple monitoring (2022)
#62I was recently looking for an ultra minimal monitoring solution for OpenWrt and other lightweight systems (Pi’s, etc.) and was disappointed not to find one that met my needs (negligible CPU, disk space and RAM). I ended up hacking together a shell script to send data to Home Assistant (via MQTT) which runs on pretty much any system that has at least netcat: https://github.com/roger-/hass-sysmon
Did you have a look at https://www.monitorix.org/ ? I'm not sure if it works on OpenWRT, but otherwise checks all the boxes.
Re: μMon: Stupid simple monitoring (2022)
#63I like the idea of simplicity and doing exactly what you need. And the single executable. The words "stupid simple" and "C++" together make me scratch my head though. C++ itself is not simple, and you have to recompile if you need to change something (and sometimes you inevitably do), which is slow. I'd likely go with a relatively simple C program that embeds the FFI for RRDtool and other stuff, and embeds Lua, or, b…
Simple means simple for the end users. Not necessarily simple for the developers. The end users do not care if the dev has to spend a couple of minutes recompiling, as long as the result is fast and simple to use.
This is fair.
But the developer and the user is one and the same here :)
Re: μMon: Stupid simple monitoring (2022)
#64Nice nifty project, he had me until the "no alerting" part. Anyway, I might still deploy this in a Proxmox homelab where I don't want to fight with the complexity of a grafana dashboard.
What’s missing from the Proxmox charts that you would need a dashboard for?
From the top of my mind (I'm not near the deployment right now):
- Temperatures
- Fan speeds
- Centralized metrics for all VMs
Re: μMon: Stupid simple monitoring (2022)
#65Earlier quoted context omitted.
I've been struggling with graphana and netdata looks so much better. Is this a tool where you can boot up the docker app and then connect a bunch of servers into a centralized dashboard? Or, is it better to think of netdata as a dashboard for a single server that permits monitoring of a bunch of processes only on that machine? I'm not sure I understand whether agents can be configured to talk to a dashboard, or if yo…
If you connect your servers to the netdata cloud, you can manage all of them there. (Put into groups etc). As far as I know there is no self hosted solution for this. https://learn.netdata.cloud/docs/configuring/connect-agent-t...
Hey - i work for Netdata on ML.
We have recently created enterprise self hosted options for bigger customers who can't use cloud etc. (prob not as relevant here)
For self hosted at a smaller scale then you can have your own parent with multiple children streaming to it.
This is an example demo node which is also a parent for some other demo nodes. None of these need to be claimed to or signed in to cloud:
https://sanfrancisco.my-netdata.io/
It uses the same actual dashboard as cloud so that we only have one dashboard to maintain so you get the cloud dashboard locally basically and the parent can then kind of act like its own little Netdata Cloud.
A handful of features not available this way since they depend on the metadata being stored in cloud as opposed to on a parent node but we are trying to bridge that gap where possible such that the metadata could actually live on a parent.
Re: μMon: Stupid simple monitoring (2022)
#66I like the concept of simple monitoring. Simple means it is simple to install, simple to maintain and simple to use. For me, this is netdata. Netdata could be much more, but I just install it on whatever machine and never think about it again. And when something is strange on that machine, I go to http://localhost:19999 and look around.
Back in 2017 when I had a bunch of physical machines and unmanaged VMs we ended up putting netdata on the servers. The reason why was because most of the team was used to manually logging onto servers and diagnosing the issue manually. The reason I liked it was because it exposes a standard Prometheus endpoint I can scrape and then view using something like Grafana. There are only about 20,000 Grafana dashboard modul…
you don't need to scap anything if you use netdata cloud see https://blog.netdata.cloud/introducing-netdata-source-plugin...
Re: μMon: Stupid simple monitoring (2022)
#67Re: μMon: Stupid simple monitoring (2022)
#68Earlier quoted context omitted.
I've been struggling with graphana and netdata looks so much better. Is this a tool where you can boot up the docker app and then connect a bunch of servers into a centralized dashboard? Or, is it better to think of netdata as a dashboard for a single server that permits monitoring of a bunch of processes only on that machine? I'm not sure I understand whether agents can be configured to talk to a dashboard, or if yo…
They have a concept called "Parents": > A “Parent” is a Netdata Agent, like the ones we install on all our systems, but is configured as a central node that receives, stores and processes metrics data from other Netdata “Child” nodes in our infrastructure... https://learn.netdata.cloud/docs/streaming/
hey - i work in Netdata on ML
Just to mention there is this doc too that also tries to explain various deployment strategies
e.g. stand alone: https://learn.netdata.cloud/docs/architecture/deployment-str...
Re: μMon: Stupid simple monitoring (2022)
#69I was recently looking for an ultra minimal monitoring solution for OpenWrt and other lightweight systems (Pi’s, etc.) and was disappointed not to find one that met my needs (negligible CPU, disk space and RAM). I ended up hacking together a shell script to send data to Home Assistant (via MQTT) which runs on pretty much any system that has at least netcat: https://github.com/roger-/hass-sysmon
Did you have a look at https://www.monitorix.org/ ? I'm not sure if it works on OpenWRT, but otherwise checks all the boxes.
It requires Perl, which ruled out OpenWrt devices with ~10 Kb of space.
Re: μMon: Stupid simple monitoring (2022)
#70Earlier quoted context omitted.
They have a concept called "Parents": > A “Parent” is a Netdata Agent, like the ones we install on all our systems, but is configured as a central node that receives, stores and processes metrics data from other Netdata “Child” nodes in our infrastructure... https://learn.netdata.cloud/docs/streaming/
hey - i work in Netdata on ML Just to mention there is this doc too that also tries to explain various deployment strategies e.g. stand alone: https://learn.netdata.cloud/docs/architecture/deployment-str...
actually sorry in this case its more like parent-child
https://learn.netdata.cloud/docs/architecture/deployment-str...
and just dont have to claim the nodes to Netdata Cloud if you don't want to.