Monitoring deployment templates
Track availability and inspect application health. Check probe protocols, notification credentials and retained data before configuring your monitors.
19 templates · Page 1 / 1
Bugsink
changedetection.io
Checkmate
Elasticsearch with Kibana
GlitchTip
Grafana
Deploy Grafana on Polyer to build dashboards and alerts from metrics, logs and databases. This template runs one grafana/grafana-oss service on a public domain, keeps its data and default SQLite database on a volume at /var/lib/grafana and generates the admin password. Review the untagged image, which tracks the latest release.
Grafana with PostgreSQL
Healthchecks
Observium
OpenObserve
Sessy
SigNoz
Statusnook
Traccar
Uptime Kuma
Deploy Uptime Kuma on Polyer to monitor websites, APIs and network services and get alerts when they go down. This template runs one louislam/uptime-kuma:2 service on a public domain and keeps monitors, settings and history on a volume at /app/data. Review the floating 2.x image tag before deploying.
Uptime Kuma with MariaDB
Uptime Kuma with MySQL
Web Check
How to choose
- For uptime checks and status pages, compare Uptime Kuma, Checkmate and Statusnook. Checks run from the region you deploy to, so a monitor in the same region as your app can go down with it.
- Healthchecks works in reverse: cron jobs ping it, and it alerts when a ping is missing. For exceptions sent by Sentry SDKs, Bugsink runs 2 services, while GlitchTip runs 5 and has compatibility warnings.
- Grafana visualizes data but does not collect it, so connect a data source first. OpenObserve keeps logs, metrics and traces in one service, while SigNoz spreads them over 6 services with compatibility warnings.