nightingale: Open-source alerting for your existing stack.
What problem it solves
Teams often have alert rules, event processing, and notification routing spread across separate systems and data sources. Nightingale brings these workflows together while allowing teams to keep their existing collectors, storage, and Grafana dashboards.
Key features
Alerting across existing data sources — Define alert conditions with PromQL, log queries, or SQL against metrics, logs, and database sources. Rules can be applied across multiple instances of the same data source type.
Source: README
Event processing and notification routing — Process events through conditional pipelines, including mutes, subscriptions, and label enrichment or rewriting. Route notifications to supported services, webhooks, scripts, and on-call platforms.
Source: README
Team ownership and access control — Organize rules and dashboards by business group, assign team permissions, and connect OIDC, OAuth2, LDAP, or CAS for sign-in.
Source: README, alert
Alert investigation and execution history — Review evaluation queries and results, active and historical events, and notification delivery records to understand why an alert fired or whether it reached its destination.
Source: README
Built-in AI agent and MCP server — Use the in-product AI agent to inspect monitoring data, troubleshoot alerts, and propose configuration changes. External assistants can access Nightingale tools through its MCP server using the caller's existing API permissions.
Source: README
Quick start
Copied verbatim from the project's README.
git clone https://github.com/ccfos/nightingale.git
cd nightingale/docker/compose-bridge
docker compose up -dWho it may suit
Inference: Nightingale may suit teams operating metrics, logs, and databases across existing monitoring infrastructure who want centralized alerting, event routing, and self-hosted control. It may also suit operators who want an AI-assisted workflow for alert investigation and configuration.
Topics to discuss
Which existing data sources and notification destinations should receive first-class support in your deployment workflows?
How should teams structure business groups, permissions, and notification routing across multiple Nightingale instances?
Which monitoring procedures are most useful to package as custom Skills for the built-in AI agent?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/ccfos/nightingale#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…