Selfhosted

39435 readers

2 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Why Prometheus + Grafana over other monitoring options? (discuss.tchncs.de)

submitted 3 months ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

I've been setting up and testing prometheus and grafana for about a week now, since that seems to be the universally accepted solution for self-hosted monitoring. But I'm starting to question why it is so accepted. On top of prometheus not seeming useful on it's own (needing grafana to visualize and alertmanager for alerts) it feels like with each thing i want to monitor I have to spin up another docker container to export/gather the data. There are other options like LibreNMS that seems to have all that built into one container. So what does this Prometheus/Grafana stack have that other monitoring services don't? Is it really worth having to set up each of these specialized exporters and dashboards? Or am I mistaken that it's the main solution everyone uses? Are you using something different for monitoring?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 3 months ago

Separate components that do one thing and only that thing and does it well are good. Extra containers are basically free.

The exporters provide the metrics. They can be standalone executables like the node exporter, can also be included in apps themselves easily since it's just HTTP. It's trivial to add metrics to just about anything without needing extra ports. Its protocol is also easier and more efficient than SNMP.
Prometheus scrapes those metrics and stores it into its database. In other apps that'd be the role things like PostgreSQL have: you don't really use it directly, but it's no less important.
Grafana is the frontend you slap in front of Prometheus to actually display your metrics.
Alertmanager looks at the metrics and sends alerts. It's separate because if your Prometheus box goes down, how are you gonna be alerted of that?

All 4 of those can be swapped with something else equivalent and it all still works. Don't like the UI? Replace Grafana. Don't like Prometheus? There's VictoriaMetrics and InfluxDB

It looks silly on a small scale, but it scales up very well. Couple hundred VMs per Prometheus install, node exporters on every VM and a single Grafana cluster to visualize the data for the whole infrastructure at once.

That makes it all well liked in enterprise which means there are exporters for damn near anything (even the Lemmy server has a built-in exporter I can scrape with Prometheus), which in turn makes it the easy solution for self-hosters too, and here we are.

I feel like it's easier to set up than some of the all in one solutions I've used previously, despite being several components. They're all components that basically just work out of the box.