📄️ Alert Management Overview
SkyLogs provides a centralized alert management system that collects, processes, and routes alerts from multiple monitoring systems.
📄️ Creating & Managing Alerts
SkyLogs provides a flexible and powerful alert management system designed to work seamlessly with multiple datasources such as Prometheus, VictoriaMetrics, Elasticsearch, and others.
📄️ API Alert
Overview
📄️ Notification Alert Rule
Overview
📄️ Prometheus Alert
Overview
📄️ Grafana Alert
A Grafana alert rule matches alerts coming from a connected Grafana instance. Alerts are ingested through the Grafana integration (a webhook contact point); this rule tells Skylogs which of those incoming alerts belong to it.
📄️ PMM Alert
Overview
📄️ Elasticsearch Alert
An Elastic alert rule fires a document-count threshold check on an Elastic/ELK data view — for example, alerting when the number of 5xx responses or error log lines in a window exceeds a limit. It's a different shape from the Prometheus/Grafana/PMM rules: there's no dynamic/text-query choice, and no external ingestion webhook is required — Skylogs runs the check itself against the connected Elastic data source. (Kibana alerting can also push events in via a webhook connector, see Elastic integration, if you prefer Kibana to own the rule instead.)
📄️ Health Check Alert
A health check alert (also called a dead-man's-switch or heartbeat alert) flips the usual model: instead of firing when something goes wrong, it fires when an expected check-in stops arriving. It's the recommended way to monitor Skylogs itself — see Admin guide → Monitoring Skylogs itself — and works just as well for any external job or service that should "phone home" on a schedule (cron jobs, backups, sync tasks).