Deploy Now

SaaS Alternative

Datadog New Relic Grafana Cloud

Stars

13,365

Forks

1,786

Watchers

170

Nightingale

When a query crosses its threshold, Nightingale, a self-hosted alerting engine, decides who hears about it and how, without moving data out of the stores you already run. Rules use PromQL, log queries, or SQL against Prometheus, VictoriaMetrics, Elasticsearch, Loki, ClickHouse, MySQL, or PostgreSQL, graded S1, S2, or S3 with a for-duration that absorbs brief spikes. Existing Prometheus alert rules import from YAML. Business groups give each team its own rules and dashboards, and sign-in works through OIDC, OAuth2, LDAP, or CAS. Once a rule fires, mute rules silence the noise, subscriptions add recipients, and event pipelines rewrite labels or route conditionally. Delivery reaches Slack, PagerDuty, Discord, Telegram, Jira, email, DingTalk, Feishu, WeCom, SMS, and voice calls, plus HTTP webhooks and scripts for anything else. Evaluation records, active and historical events, and notification results show what happened at each step. If an alert misbehaves, the built-in AI agent explains why it fired or never arrived, and it drafts rules, dashboards, and mutes from plain-language requests. Claude Code, Cursor, and other MCP clients can query alerts and manage alerting through /mcp, read-only by default and bound by the caller's own permissions. At remote sites, n9e-edge keeps evaluating and notifying when the link to the center drops. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Nightingale
Nightingale
Nightingale
Nightingale
Nightingale
Nightingale
Nightingale

Benefits

  • Alerting without moving your data
  • Nightingale queries Prometheus, VictoriaMetrics, Elasticsearch, Loki, ClickHouse, and SQL databases where they already live, so adopting it needs no migration and keeps your existing collectors, storage, and Grafana dashboards.
  • Cut noise before anyone is paged
  • Mute rules, subscriptions, and event pipelines filter and rewrite events before delivery, while for-durations absorb brief spikes and S1 to S3 severities rank what deserves a page.
  • Trace every alert to delivery
  • Evaluation records, active and historical events, and notification results show which query fired, what value triggered it, and whether Slack, PagerDuty, or email actually received the message.
  • AI agent and MCP built in
  • The n9e process runs its own AI agent and serves an MCP server at /mcp, so Claude Code, Cursor, and other clients manage alerting with no extra service to deploy.

Features

  • Multi-Source Alert Rules
  • Define conditions with PromQL, log queries, or SQL against Prometheus, VictoriaMetrics, Elasticsearch, Loki, ClickHouse, MySQL, and PostgreSQL, graded S1, S2, or S3 inside business groups.
  • Event Processing Pipelines
  • Mute rules, subscriptions, label rewriting, and conditional routing filter events before delivery to Slack, PagerDuty, Discord, Telegram, Jira, Email, DingTalk, Feishu, WeCom, or webhooks.
  • Teams and Single Sign-On
  • Business groups scope rules and dashboards to teams with role-based permissions, and sign-in works through OIDC, OAuth2, LDAP, or CAS for central identity control.
  • Built-In AI Agent
  • Chat with an agent that inspects metrics, logs, rules, and evaluation records, drafts alert rules and dashboards, and loads custom Skills; it connects to OpenAI-compatible APIs, Claude, or Gemini.
  • Built-In MCP Server
  • A Streamable HTTP endpoint at /mcp exposes alerting tools to Claude Code, Cursor, and other MCP clients, with read tools by default and write tools only when enabled.
  • Edge Evaluation and Remediation
  • n9e-edge evaluates rules close to remote data sources through network partitions, and ibex runs predefined remediation scripts automatically when an alert fires.

Apps Similar to Nightingale