Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: removing email from receivers #100

Merged
merged 2 commits into from
Feb 5, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/apps/alertmanager.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand All @@ -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).

1 change: 0 additions & 1 deletion docs/for-devs/console/settings.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
1 change: 0 additions & 1 deletion docs/for-ops/console/settings/alerts.md
Original file line number Diff line number Diff line change
Expand Up @@ -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) |
2 changes: 1 addition & 1 deletion docs/for-ops/console/teams.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down