From 34ebdad9fe39eb4e331da930a44d9e2b8f2acccb Mon Sep 17 00:00:00 2001 From: Ani Argjiri Date: Wed, 5 Feb 2025 10:42:44 +0100 Subject: [PATCH] feat: removing email from receivers (#100) --- docs/apps/alertmanager.md | 3 +-- docs/for-devs/console/settings.md | 1 - docs/for-ops/console/settings/alerts.md | 1 - docs/for-ops/console/teams.md | 2 +- 4 files changed, 2 insertions(+), 5 deletions(-) diff --git a/docs/apps/alertmanager.md b/docs/apps/alertmanager.md index 779ae8bc7..a6d4644d0 100644 --- a/docs/apps/alertmanager.md +++ b/docs/apps/alertmanager.md @@ -6,7 +6,7 @@ sidebar_label: Alertmanager ## About -Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of de-duplicating, grouping, and routing them to the correct receiver integration such as email, Slack, MS Teams, or OpsGenie. It also takes care of silencing and inhibition of alerts. +Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of de-duplicating, grouping, and routing them to the correct receiver integration such as Slack, MS Teams, or OpsGenie. It also takes care of silencing and inhibition of alerts. Alertmanager is configured to use the global values found under settings' [alerts](../for-ops/console/settings/alerts.md). @@ -17,6 +17,5 @@ The following receivers are supported: - `Slack` - `Microsoft Teams` - `Ops Genie` -- `Email` - (default) `None` (will use the `null` receiver to enable the Alertmanager UI). diff --git a/docs/for-devs/console/settings.md b/docs/for-devs/console/settings.md index 91ef16bd4..0595f9bb7 100644 --- a/docs/for-devs/console/settings.md +++ b/docs/for-devs/console/settings.md @@ -54,7 +54,6 @@ Change the alert settings and preferred notification receivers. | ---------------- | -------------------------------------------------------------------------------- | | Slack | Needs a slack webhook url that will give alerts for warnings and criticals | | Microsoft Teams | Needs two alerting endpoints, for both warnings as well as criticals | -| Email | You may provide a list of email addresses for both 'Non Critical' and 'Critical' | | If none selected | Global (admin) alerting endpoint configuration will be used | ## Configure Resource Quotas diff --git a/docs/for-ops/console/settings/alerts.md b/docs/for-ops/console/settings/alerts.md index 9a2ace25d..128a3bdc3 100644 --- a/docs/for-ops/console/settings/alerts.md +++ b/docs/for-ops/console/settings/alerts.md @@ -24,5 +24,4 @@ The alerts settings section offers configuration options to define alerting endp | ------- | ----------- | | Slack | Slack webhook URL and channels for critical and non-critical alerts. | | Msteams | Microsoft Teams webhook URLs for critical (high prio) and non-critical alerts (low prio). | -| Email | Email address(es) for critical and non-critical alerts. | | Opsgenie | Opsgenie API Key, URL and alert responder(s) | diff --git a/docs/for-ops/console/teams.md b/docs/for-ops/console/teams.md index 35962e95a..8f6164426 100644 --- a/docs/for-ops/console/teams.md +++ b/docs/for-ops/console/teams.md @@ -12,7 +12,7 @@ sidebar_label: Teams - A Team will get access to the Console, providing access to self-service features and all the shared apps available on the platform. -- Teams can choose to receive alerts in Microsoft Teams, Slack or email and each team will get access to a project in Harbor. +- Teams can choose to receive alerts in Microsoft Teams or Slack or Ops Genie and each team will get access to a project in Harbor. - Teams can be allowed self-service features like configure ingress, configure a notification receiver for alerts, change the OIDC group mappings and download the KubeConfig.