Status Page
Lynx Status Page
Public status and incident page fed by pluggable monitoring connectors (Zabbix, Datadog, PagerDuty, New Relic, Prometheus and manual webhooks).
lynx_status_page
· v19.0.1.4.0
· Standard
Beta
What this solves
Lynx Status Page
A public status and incident communication page — a self-hosted replacement for hosted status pages — whose component health is driven by the monitoring platforms a team already runs. A component is bound to a saved connector through a status source, and each poll translates the platform's signal (a Zabbix problem severity, a Datadog monitor state, a PagerDuty service status, a New Relic alert severity, a Prometheus alert) into an operational, degraded or outage status. Tools without a connector post status through an authenticated webhook.
The public page is served at /status with no website app required; incident timelines, scheduled maintenance and 90-day uptime render from the same data as a StatusPage-style JSON API, an RSS feed and a status badge.
Key Features
Pages and components - group components under a branded page with a derived overall status and 90-day uptime from status-change history.
Monitoring sources - bind a component to a lynx.connector pull; a per-type threshold turns the signal into a component status on a cron.
Incidents - investigating / identified / monitoring / resolved lifecycle with a posted-update timeline that notifies subscribers.
Scheduled maintenance - windows with affected components shown publicly.
Subscribers - double opt-in email subscriptions with unsubscribe links.
Public API - StatusPage-style summary/components/incidents JSON, an RSS history feed, a status badge SVG and a token-guarded push webhook.
Integrates With
lynx_connectors and the lynx_connector_* cores - the source of component health.
lynx_status_page_website - re-homes the public page in the site layout when a website is installed.
Try Lynx Status Page on your team.
Free trial, no credit card. Talk to sales when you're ready.