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
Copy file name to clipboardexpand all lines: docs/setup_installation/admin/alert.md
+11-2
Original file line number
Diff line number
Diff line change
@@ -82,17 +82,26 @@ Click on the _Configure_ button on the left side of the **webhook** row and fill
82
82
83
83
Fill in the unique URL of your Webhook: the endpoint to send HTTP POST requests to.
84
84
85
-
A global receiver is created when a webhook is configured.
85
+
A global receiver is created when a webhook is configured and can be used by any project in the cluster.
86
86
87
87
### Step 6: Advanced configuration
88
88
If you are familiar with Prometheus' [Alert manager](https://prometheus.io/docs/alerting/latest/alertmanager/)
89
-
you can also configure alerts by editing the _yaml/json_ file directly.
89
+
you can also configure alerts by editing the _yaml/json_ file directly by going to the advaced page and clicking the edit button.
90
+
91
+
The advanced page shows the configuration currently loaded on the alert manager. After editing the configuration it takes some time to propagate changes to the alertmanager.
92
+
93
+
The reload button can be used to validate the changes made to the configuration.
94
+
It will try to load the new configuration to the alertmanager and show any errors that might prevent the configuration from being loaded.
If you make any changes to the configuration ensure that the changes are valid by reloading the configuration until the changes are loaded and visible in the advanced page.
104
+
96
105
_Example:_ Adding the yaml snippet shown below in the global section of the alert manager configuration will
97
106
have the same effect as creating the SMTP configuration as shown in [section 1](#1-email-alerts) above.
0 commit comments