Go to file
710leo 52b3afbd97 fix: recovery event tags map split 2024-09-22 19:14:24 +08:00
.github add link in github issue template 2024-06-13 15:54:24 +08:00
alert fix: recovery event tags map split 2024-09-22 19:14:24 +08:00
center fix: recovery event tags map split 2024-09-22 19:14:24 +08:00
cli update ops 2023-06-15 11:22:26 +08:00
cmd fix: edge host miss alert 2024-05-30 16:57:04 +08:00
conf feat: Integration ibex (#1904) 2024-04-06 22:02:07 +08:00
cron feat: support record event notify detail (#2088) 2024-08-09 17:06:49 +08:00
doc update logo 2023-11-11 22:21:15 +08:00
docker docs: add target_busi_group sql 2024-09-20 18:14:15 +08:00
dumper rename obs to dumper 2023-07-17 07:04:01 +08:00
etc feat: support sqlite (#1978) 2024-06-05 17:28:56 +08:00
front/statik refactor: update targets api 2024-08-26 20:34:04 +08:00
integrations docs: update linux metrics tpl 2024-09-13 19:10:33 +08:00
memsto fix: edge target cache 2024-09-22 00:33:28 +08:00
models fix: recovery event tags map split 2024-09-22 19:14:24 +08:00
pkg feat: trigger set support operation (#2107) 2024-08-21 20:16:31 +08:00
prom refactor: timeteries handle hook (#1772) 2023-11-08 15:11:39 +08:00
pushgw refactor: update append_labels 2024-09-20 16:24:47 +08:00
storage Remove duplicate fields UseTLS 2024-09-21 20:44:02 +08:00
tdengine refactor: alert eval (#1855) 2024-01-30 18:08:37 +08:00
.gitattributes add tsx 2020-04-07 20:30:22 +08:00
.gitignore docs: add docker-compose files for logs processing (#1819) 2024-01-04 19:23:05 +08:00
.goreleaser.yaml code refactor 2023-06-01 21:09:04 +08:00
LICENSE v6 release 2023-03-09 17:43:51 +08:00
Makefile use standard http client instead of beego client 2023-06-02 09:58:10 +08:00
README.md Update README.md wechat qrcode 2024-09-18 08:13:42 +08:00
README_en.md update readme_en (#2099) 2024-08-14 12:20:11 +08:00
fe.sh code refactor 2023-11-15 10:33:38 +08:00
go.mod feat: support clone rules by idents (#2095) 2024-08-13 19:12:31 +08:00
go.sum feat: support clone rules by idents (#2095) 2024-08-13 19:12:31 +08:00

README_en.md

nightingale - cloud native monitoring

Open-source Alert Management Expert, an Integrated Observability Platform

Docs Docker pulls GitHub contributors GitHub Repo stars GitHub forks
GitHub Repo issues GitHub Repo issues closed GitHub latest release License GitHub contributors

English | 中文

What is Nightingale

Nightingale aims to combine the advantages of Prometheus and Grafana. It manages alert rules and visualizes metrics, logs, traces in a beautiful WebUI.

Originally developed and open-sourced by Didi, Nightingale was donated to the China Computer Federation Open Source Development Committee (CCF ODC) on May 11, 2022, becoming the first open-source project accepted by the CCF ODC after its establishment.

Quick Start

Features

  • Integration with Multiple Time-Series Databases: Supports integration with various time-series databases such as Prometheus, VictoriaMetrics, Thanos, Mimir, M3DB, and TDengine, enabling unified alert management.
  • Advanced Alerting Capabilities: Comes with built-in support for multiple alerting rules, extensible to common notification channels. It also supports alert suppression, silencing, subscription, self-healing, and alert event management.
  • High-Performance Visualization Engine: Offers various chart styles with numerous built-in dashboard templates and the ability to import Grafana templates. Ready to use with a business-friendly open-source license.
  • Support for Common Collectors: Compatible with Categraf, Telegraf, Grafana-agent, Datadog-agent, and various exporters as collectors—there's no data that can't be monitored.
  • Seamless Integration with Flashduty: Enables alert aggregation, acknowledgment, escalation, scheduling, and IM integration, ensuring no alerts are missed, reducing unnecessary interruptions, and enhancing efficient collaboration.

Screenshots

You can switch languages and themes in the top right corner. We now support English, Simplified Chinese, and Traditional Chinese.

18n switch

Instant Query

Similar to the built-in query analysis page in Prometheus, Nightingale offers an ad-hoc query feature with UI enhancements. It also provides built-in PromQL metrics, allowing users unfamiliar with PromQL to quickly perform queries.

Instant Query

Metric View

Alternatively, you can use the Metric View to access data. With this feature, Instant Query becomes less necessary, as it caters more to advanced users. Regular users can easily perform queries using the Metric View.

Metric View

Built-in Dashboards

Nightingale includes commonly used dashboards that can be imported and used directly. You can also import Grafana dashboards, although compatibility is limited to basic Grafana charts. If youre accustomed to Grafana, its recommended to continue using it for visualization, with Nightingale serving as an alerting engine.

Built-in Dashboards

Built-in Alert Rules

In addition to the built-in dashboards, Nightingale also comes with numerous alert rules that are ready to use out of the box.

Built-in Alert Rules

Architecture

In most community scenarios, Nightingale is primarily used as an alert engine, integrating with multiple time-series databases to unify alert rule management. Grafana remains the preferred tool for visualization. As an alert engine, the product architecture of Nightingale is as follows:

Product Architecture

For certain edge data centers with poor network connectivity to the central Nightingale server, we offer a distributed deployment mode for the alert engine. In this mode, even if the network is disconnected, the alerting functionality remains unaffected.

Edge Deployment Mode

Communication Channels

Stargazers over time

Stargazers over time

Community Co-Building

  • ❇️ Please read the Nightingale Open Source Project and Community Governance Draft. We sincerely welcome every user, developer, company, and organization to use Nightingale, actively report bugs, submit feature requests, share best practices, and help build a professional and active open-source community.
  • ❤️ Nightingale Contributors

License