Prometheus - monitoring & time series database
-
And AlertManager:
"The Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integration such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts."
https://prometheus.io/docs/alerting/latest/alertmanager/
https://github.com/prometheus/alertmanager -
After installing Grafana on Cloudron, I'd really like this too!
-
@eriktad said in Prometheus - monitoring & time series database:
@girish https://git.cloudron.io/erik/alertmanager-app and Alertmanager app
I don't have much experience with Promotheus. Does it make sense to merge alertmanager into the main app itself or do you think it should be separate apps?
If you need help deciding, we can take a guess from how they are usually deployed? Are they in separate domains or as subpaths etc.
-
@girish Yeh, I thought about that but idk, they run on other ports and have other dashboards, but altermanager only alerting Prometheus massages, I can try to merge, think it is good idea, but we need to understand if user no need alerts why we setup it with Prometheus.
-
@eriktad They make sense as separate Apps.
I'd suggest the App naming would make it clearer, so:
- Prometheus Server
- Prometheus Alertmanager
- Thanos (Single-Node)
For interest, like Statping, in mission-critical setups it makes sense to have Prometheus running on a separate Cloudron instance for continuity of data-gathering throughout the ups & downs of the services being monitored.
-
@eriktad Thanks for packaging the app. I have published the app as unstable currently. https://git.cloudron.io/cloudron/prometheus-app/ is the repo. I removed the apache authentication bits because I have now merged the "auth wall" feature in Cloudron 6. With that feature, we can just add proxyAuth to the manifest and we will immediately get a login screen (so we don't need to put these things as part of the app).