Go to file
Ulric Qin ab689fc0db update README 2022-06-08 11:12:51 +08:00
.github modify github template 2021-12-09 14:22:39 +08:00
doc update README 2022-06-08 11:12:51 +08:00
docker fix:pg数据库脚本同步 (#974) 2022-06-06 11:48:57 +08:00
etc fix: linux_by_telegraf dashboard 2022-06-07 14:17:17 +08:00
src code refactor: move struct ReaderOptions to config 2022-06-07 18:00:11 +08:00
.gitattributes add tsx 2020-04-07 20:30:22 +08:00
.gitignore modify n9eetc dir 2021-12-08 23:55:51 +08:00
LICENSE init project 2020-03-11 18:25:20 +08:00
Makefile add header for writer post 2022-06-07 17:56:23 +08:00
README.md update README 2022-06-08 11:12:51 +08:00
README_EN.md update README 2022-06-08 11:12:51 +08:00
go.mod use go1.18 and tidy go.mod 2022-05-30 09:08:54 +08:00
go.sum use go1.18 and tidy go.mod 2022-05-30 09:08:54 +08:00

README_EN.md

Nightingale is an enterprise-level cloud-native monitoring system, which can be used as drop-in replacement of Prometheus for alerting and management.

English | 中文

Introduction

Nightingale is an cloud-native monitoring system by All-In-On design, support enterprise-class functional features with an out-of-the-box experience. We recommend upgrading your Prometheus + AlertManager + Grafana combo solution to Nightingale.

  • Multiple prometheus data sources management: manage all alerts and dashboards in one centralized visually view;
  • Out-of-the-box alert rule: built-in multiple alert rules, reuse alert rules template by one-click import with detailed explanation of metrics;
  • Multiple modes for visualizing data: out-of-the-box dashboards, instance customize views, expression browser and Grafana integration;
  • Multiple collection clients: support using Promethues Exporter、Telegraf、Datadog Agent to collecting metrics;
  • Integration of multiple storage: support Prometheus, M3DB, VictoriaMetrics, Influxdb, TDEngine as storage solutions, and original support for PromQL;
  • Fault self-healing: support the ability to self-heal from failures by configuring webhook;
  • Multiple systems such as Prometheus, Alertmanager, Grafana, etc. are fragmented and lack a unified view and cannot be used out of the box;
  • The way to manage Prometheus and Alertmanager by modifying configuration files has a big learning curve and is difficult to collaborate;
  • Too much data to scale-up your Prometheus cluster;
  • Multiple Prometheus clusters running in production environments, which faced high management and usage costs;
  • Monitoring too much data and wanting a better scalable solution;
  • A high learning curve and a desire for better efficiency of collaborative use in a multi-person, multi-team model;
  • Microservice and cloud-native architectures with variable monitoring data lifecycles and high monitoring data dimension bases, which are not easily adaptable to the Zabbix data model;

If you are using open-falcon, we recommend you to upgrade to Nightingale

Quickstart

Documentation

Example of use

You can also easily view all active alerts and historical alerts in Nightingale:

System Architecture

A typical Nightingale deployment architecture:

Typical deployment architecture using VictoriaMetrics as storage:

Contact us and feedback questions

Contributing

We welcome your participation in the Nightingale open source project and open source community in a variety of ways:

License

Nightingale with Apache License V2.0 open source license.