From 3855e5a331e442b56e0665c1ea019608340badef Mon Sep 17 00:00:00 2001 From: Denise Schannon Date: Mon, 9 Jul 2018 20:52:38 -0700 Subject: [PATCH] alerts and notifiers concepts --- .../concepts/alerts-and-notifiers/_index.md | 31 +++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/content/rancher/v2.x/en/concepts/alerts-and-notifiers/_index.md b/content/rancher/v2.x/en/concepts/alerts-and-notifiers/_index.md index 1538a3ffe5b..de5c31fa308 100644 --- a/content/rancher/v2.x/en/concepts/alerts-and-notifiers/_index.md +++ b/content/rancher/v2.x/en/concepts/alerts-and-notifiers/_index.md @@ -3,3 +3,34 @@ title: Alerts and Notifiers weight: 2300 draft: true --- + +Alerts and notifications are built on top of the [Prometheus Alertmanager](https://prometheus.io/docs/alerting/alertmanager/). Leveraging these tools, Rancher is able to provide the first step in notifications for events operators and application owners need to know about. + +## Notifiers + +In Rancher 2.x, a user can configure `Notifiers` for each cluster that can receive alerts for various events. By configuring the notifiers at the cluster level, project owners do not need to know SMTP settings or have access to cloud accounts. At a project level, users can configure alerts and add recipients scoped to the relevant alerts. + +Available Notifiers: + +* Email +* Slack +* PagerDuty +* Webhooks + +## Alerts + +Rancher supports alerting on a cluster level or project level. + +On a cluster level, Rancher can monitor and alert on components that manage your Kubernetes cluster including: + +* System Services +* Resource Events +* Node conditions + +Operators of Kubernetes clusters can get alerts on the health of nodes and other system level components. + +On a project level, Rancher can monitor and alert on status on specific deployments including: + +* Deployment availability +* Workloads +* Pods