@cryptotaxi247 / netdata-1 / commits / 39badb8e0

Regenerate integrations.js (#18454)

Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>

Netdata bot committed Sep 1, 2024 at 12:44 UTC 39badb8e0dac1b8fda14692f96355c7fb8cbb6dd
3 files changed +134
integrations/integrations.js
+19
@@ -21806,6 +21806,25 @@ export const integrations = [
21806 "integration_type": "notification",
21807 "edit_link": "https://github.com/netdata/netdata/blob/master/src/health/notifications/gotify/metadata.yaml"
21808 },
21809 + {
21810 + "id": "notify-ilert",
21811 + "meta": {
21812 + "name": "ilert",
21813 + "link": "https://www.ilert.com/",
21814 + "categories": [
21815 + "notify.agent"
21816 + ],
21817 + "icon_filename": "ilert.svg"
21818 + },
21819 + "keywords": [
21820 + "ilert"
21821 + ],
21822 + "overview": "# ilert\n\nilert is an alerting and incident management tool. It helps teams reduce response times by enhancing monitoring and ticketing tools with reliable alerts, automatic escalations, on-call schedules, and features for incident response, communication, and status updates.\nSending notification to ilert via Netdata's Agent alert notification feature includes links, images and resolving of corresponding alerts.\n\n",
21823 + "setup": "## Setup\n\n### Prerequisites\n\n#### \n\n- A Netdata alert source in ilert. You can create a [Netdata alert source](https://docs.ilert.com/inbound-integrations/netdata) in [ilert](https://www.ilert.com/).\n- Access to the terminal where Netdata Agent is running\n\n\n\n### Configuration\n\n#### File\n\nThe configuration file name for this integration is `health_alarm_notify.conf`.\n\n\nYou can edit the configuration file using the `edit-config` script from the\nNetdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).\n\n```bash\ncd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata\nsudo ./edit-config health_alarm_notify.conf\n```\n#### Options\n\nThe following options can be defined for this notification\n\n{% details open=true summary=\"Config Options\" %}\n| Name | Description | Default | Required |\n|:----|:-----------|:-------|:--------:|\n| SEND_ILERT | Set `SEND_ILERT` to YES | YES | yes |\n| ILERT_ALERT_SOURCE_URL | Set `ILERT_ALERT_SOURCE_URL` to your Netdata alert source url in ilert. | | yes |\n\n{% /details %}\n#### Examples\n\n##### Basic Configuration\n\n\n\n```yaml\nSEND_ILERT=\"YES\"\nILERT_ALERT_SOURCE_URL=\"https://api.ilert.com/api/v1/events/netdata/{API-KEY}\"\n\n```\n",
21824 + "troubleshooting": "## Troubleshooting\n\n### Test Notification\n\nYou can run the following command by hand, to test alerts configuration:\n\n```bash\n# become user netdata\nsudo su -s /bin/bash netdata\n\n# enable debugging info on the console\nexport NETDATA_ALARM_NOTIFY_DEBUG=1\n\n# send test alarms to sysadmin\n/usr/libexec/netdata/plugins.d/alarm-notify.sh test\n\n# send test alarms to any role\n/usr/libexec/netdata/plugins.d/alarm-notify.sh test \"ROLE\"\n```\n\nNote that this will test _all_ alert mechanisms for the selected role.\n\n",
21825 + "integration_type": "notification",
21826 + "edit_link": "https://github.com/netdata/netdata/blob/master/src/health/notifications/ilert/metadata.yaml"
21827 + },
21828 {
21829 "id": "notify-irc",
21830 "meta": {
integrations/integrations.json
+19
@@ -21804,6 +21804,25 @@
21804 "integration_type": "notification",
21805 "edit_link": "https://github.com/netdata/netdata/blob/master/src/health/notifications/gotify/metadata.yaml"
21806 },
21807 + {
21808 + "id": "notify-ilert",
21809 + "meta": {
21810 + "name": "ilert",
21811 + "link": "https://www.ilert.com/",
21812 + "categories": [
21813 + "notify.agent"
21814 + ],
21815 + "icon_filename": "ilert.svg"
21816 + },
21817 + "keywords": [
21818 + "ilert"
21819 + ],
21820 + "overview": "# ilert\n\nilert is an alerting and incident management tool. It helps teams reduce response times by enhancing monitoring and ticketing tools with reliable alerts, automatic escalations, on-call schedules, and features for incident response, communication, and status updates.\nSending notification to ilert via Netdata's Agent alert notification feature includes links, images and resolving of corresponding alerts.\n\n",
21821 + "setup": "## Setup\n\n### Prerequisites\n\n#### \n\n- A Netdata alert source in ilert. You can create a [Netdata alert source](https://docs.ilert.com/inbound-integrations/netdata) in [ilert](https://www.ilert.com/).\n- Access to the terminal where Netdata Agent is running\n\n\n\n### Configuration\n\n#### File\n\nThe configuration file name for this integration is `health_alarm_notify.conf`.\n\n\nYou can edit the configuration file using the `edit-config` script from the\nNetdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).\n\n```bash\ncd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata\nsudo ./edit-config health_alarm_notify.conf\n```\n#### Options\n\nThe following options can be defined for this notification\n\n| Name | Description | Default | Required |\n|:----|:-----------|:-------|:--------:|\n| SEND_ILERT | Set `SEND_ILERT` to YES | YES | yes |\n| ILERT_ALERT_SOURCE_URL | Set `ILERT_ALERT_SOURCE_URL` to your Netdata alert source url in ilert. | | yes |\n\n#### Examples\n\n##### Basic Configuration\n\n\n\n```yaml\nSEND_ILERT=\"YES\"\nILERT_ALERT_SOURCE_URL=\"https://api.ilert.com/api/v1/events/netdata/{API-KEY}\"\n\n```\n",
21822 + "troubleshooting": "## Troubleshooting\n\n### Test Notification\n\nYou can run the following command by hand, to test alerts configuration:\n\n```bash\n# become user netdata\nsudo su -s /bin/bash netdata\n\n# enable debugging info on the console\nexport NETDATA_ALARM_NOTIFY_DEBUG=1\n\n# send test alarms to sysadmin\n/usr/libexec/netdata/plugins.d/alarm-notify.sh test\n\n# send test alarms to any role\n/usr/libexec/netdata/plugins.d/alarm-notify.sh test \"ROLE\"\n```\n\nNote that this will test _all_ alert mechanisms for the selected role.\n\n",
21823 + "integration_type": "notification",
21824 + "edit_link": "https://github.com/netdata/netdata/blob/master/src/health/notifications/ilert/metadata.yaml"
21825 + },
21826 {
21827 "id": "notify-irc",
21828 "meta": {
src/health/notifications/ilert/README.md new
+96
@@ -0,0 +1,96 @@
1 +<!--startmeta
2 +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/health/notifications/ilert/README.md"
3 +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/health/notifications/ilert/metadata.yaml"
4 +sidebar_label: "ilert"
5 +learn_status: "Published"
6 +learn_rel_path: "Alerts & Notifications/Notifications/Agent Dispatched Notifications"
7 +message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NOTIFICATION'S metadata.yaml FILE"
8 +endmeta-->
9 +
10 +# ilert
11 +
12 +
13 +<img src="https://netdata.cloud/img/ilert.svg" width="150"/>
14 +
15 +
16 +ilert is an alerting and incident management tool. It helps teams reduce response times by enhancing monitoring and ticketing tools with reliable alerts, automatic escalations, on-call schedules, and features for incident response, communication, and status updates.
17 +Sending notification to ilert via Netdata's Agent alert notification feature includes links, images and resolving of corresponding alerts.
18 +
19 +
20 +
21 +<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />
22 +
23 +## Setup
24 +
25 +### Prerequisites
26 +
27 +####
28 +
29 +- A Netdata alert source in ilert. You can create a [Netdata alert source](https://docs.ilert.com/inbound-integrations/netdata) in [ilert](https://www.ilert.com/).
30 +- Access to the terminal where Netdata Agent is running
31 +
32 +
33 +
34 +### Configuration
35 +
36 +#### File
37 +
38 +The configuration file name for this integration is `health_alarm_notify.conf`.
39 +
40 +
41 +You can edit the configuration file using the `edit-config` script from the
42 +Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).
43 +
44 +```bash
45 +cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
46 +sudo ./edit-config health_alarm_notify.conf
47 +```
48 +#### Options
49 +
50 +The following options can be defined for this notification
51 +
52 +<details open><summary>Config Options</summary>
53 +
54 +| Name | Description | Default | Required |
55 +|:----|:-----------|:-------|:--------:|
56 +| SEND_ILERT | Set `SEND_ILERT` to YES | YES | yes |
57 +| ILERT_ALERT_SOURCE_URL | Set `ILERT_ALERT_SOURCE_URL` to your Netdata alert source url in ilert. | | yes |
58 +
59 +</details>
60 +
61 +#### Examples
62 +
63 +##### Basic Configuration
64 +
65 +
66 +
67 +```yaml
68 +SEND_ILERT="YES"
69 +ILERT_ALERT_SOURCE_URL="https://api.ilert.com/api/v1/events/netdata/{API-KEY}"
70 +
71 +```
72 +
73 +
74 +## Troubleshooting
75 +
76 +### Test Notification
77 +
78 +You can run the following command by hand, to test alerts configuration:
79 +
80 +```bash
81 +# become user netdata
82 +sudo su -s /bin/bash netdata
83 +
84 +# enable debugging info on the console
85 +export NETDATA_ALARM_NOTIFY_DEBUG=1
86 +
87 +# send test alarms to sysadmin
88 +/usr/libexec/netdata/plugins.d/alarm-notify.sh test
89 +
90 +# send test alarms to any role
91 +/usr/libexec/netdata/plugins.d/alarm-notify.sh test "ROLE"
92 +```
93 +
94 +Note that this will test _all_ alert mechanisms for the selected role.
95 +
96 +