Im mostly looking for traffic uptime and resourses
Comment on Observability
curbstickle@anarchist.nexus 2 days ago
Depends on what youre trying to track, but prom can track whatever you want and grafana can display it. You may also want LPG monitoring ad well, which you can also feed in - grafana is just display.
The metrics you want to look at are the big question though.
DrunkAnRoot@sh.itjust.works 2 days ago curbstickle@anarchist.nexus 1 day ago
It seems to me like you don’t really want historic metrics.
Youre not looking for an observability platform, more a resource monitor like btop. Whether its btop.or one of the other variations of top, there are a lot of them with heavy customization options.
I’d recommend starting there to figure out what you want/need.
irmadlad@lemmy.world 1 day ago Btop is my favorite top of all the tops. I run it regularly just to scope how things are processing.
captcha_incorrect@lemmy.world 1 day ago
What would you recommend for historic metrics? Specifically for podman containers.
curbstickle@anarchist.nexus 1 day ago
Prometheus and Grafana are my typical recommendation there, with the podman exporter. Prometheus for time series data, Grafana to visualize and alert.
One thing I think many folks get wrong is thinking about Grafana (or any other dashboard) as the way to watch for problems, but that requires you to look at them. They should be thought of as a way to evaluate for conditions that there was a problem, then create an alert based on the indicators. This way you can address it before it becomes a problem, or at a minimum be aware that conditions are leading toward a problematic state.
If its repeatable and managed with a container restart or something, you can automate that from the alert, and never have to look again.
If its something you can’t control (for example, availability of a 3rd party service), you can use it as a way to be notified of the status change. I have a custom exporter I wrote for work to keep track of some services that result in a bunch of posts to Teams by people asking if its working for them. So I have an automation that posts to Teams when a service has a problem so my IT guy doesn’t need to respond to all of them individually.
So I’d recommend focusing on good alerts and automations over beautiful dashboards first (though dashboards can be a lot of fun to make!)
surewhynotlem@lemmy.world 1 day ago
They are useful for diagnosing recurring crashes.
WhyJiffie@sh.itjust.works 10 hours ago
Prometheus is mostly for regularly collected statistics and state. what would you recommend for statistics that are only collected when something happens? stats that aren’t available on schedule. as an example, take UPS state changes to battery mode or overvoltage mode. Prometheus can’t collect them when they are short lived.
curbstickle@anarchist.nexus 10 hours ago
Depends
To me this is where SNMP traps shine, its quite specifically its purpose. Which means alloy, logstash, snmptrapd + promtail, logstashetc. Which fits best depends on what youre doing, I personally lean simple first. Do you want traps by themselves? Remote logs? Do you have a device thats already handling relays that can be triggered? How does the UPS connect? If its serial or USB over to a dedicated machine, that machine should log and send upstream.