You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each directory contains alerting rules in YAML format. For example, the `host-and-hardware` directory includes common alerting rules for node-exporter. Want to directly import these rules into Nightingale? Please refer to the following steps.
20
+
21
+
## Version
22
+
23
+
Please use Nightingale version 8.2.0 or later.
24
+
25
+
## Import Steps
26
+
27
+

28
+
29
+
As shown in the screenshot above, go to the alerting rules page and select import to import Prometheus-format alerting rules. Note that the YAML-formatted rule content starts with `groups`, which contains multiple `group` entries. Each `group` has a `name` and `rules`, where `rules` is an array of specific alerting rules. Nightingale will ignore the `group`'s `name` during processing and directly import the content in `rules`.
30
+
31
+
After the import is complete, you usually need to associate notification rules to enable alert notifications. The method is: select the alerting rules in batches, then click "More Operations" in the upper right corner to batch update the alerting rules:
32
+
33
+

34
+
35
+
In the batch update pop-up, select "Notification rule" as the field, then choose the corresponding notification rule and click "Confirm". The screenshot is as follows:
- Nightingale supports alert rules, muting rules, subscription rules, and notification rules. It natively integrates 20 notification channels and allows customization of message templates.
58
58
- Nightingale supports event pipelines to process alert events and integrate with third-party systems. For example, it can perform operations like relabeling, filtering, and enriching on events.
59
59
- Nightingale supports the concept of business groups and introduces a permission system to manage various rules in a categorized manner.
60
60
- Many databases and middleware have built-in alert rules that can be directly imported for use, and Prometheus alert rules can also be directly imported.
61
61
- Nightingale supports alert self-healing, which means that after an alert is triggered, a script is automatically executed to perform some predefined logic, such as cleaning up the disk or capturing the on-site situation.
- Nightingale has built-in metric explanations, dashboards, and alert rules for common operating systems, middleware, and databases. However, these are all contributed by the community, and their overall quality varies.
71
71
- Nightingale directly receives data from multiple protocols such as Remote Write, OpenTSDB, Datadog, and Falcon, thus enabling integration with various types of agents.
72
72
- Nightingale supports multiple data sources including Prometheus, ElasticSearch, Loki, and TDEngine, and can perform alerting based on the data from them.
73
73
- Nightingale can be easily embedded into internal enterprise systems, such as Grafana and CMDB. It even allows configuring the menu visibility of these embedded systems.
- Nightingale supports dashboard functionality, featuring common chart types and some built-in dashboards. The image above is a screenshot of one of these dashboards.
78
78
- If you're already accustomed to Grafana, it's recommended to continue using Grafana for viewing charts, as Grafana has more profound expertise in this area.
0 commit comments