Continental Innovates with Rancher and Kubernetes
In Rancher 2.5, the notifier application was improved. There are now two ways to enable notifiers. The older way is documented in this section, and the new application for notifiers is documented here.
Notifiers are services that inform you of alert events. You can configure notifiers to send alert notifications to staff best suited to take corrective action.
Rancher integrates with a variety of popular IT services, including:
This section covers the following topics:
Notifiers are configured at the cluster level. This model ensures that only cluster owners need to configure notifiers, leaving project owners to simply configure alerts in the scope of their projects. You don’t need to dispense privileges like SMTP server access or cloud account access.
Set up a notifier so that you can begin configuring and sending alerts.
Result: Your notifier is added to Rancher.
#<channelname>
Validation: Click Test. If the test is successful, the Slack channel you’re configuring for the notifier outputs Slack setting validated.
SMTP Server Configuration:
smtp.email.com
587
465
Validation: Click Test. If the test is successful, Rancher prints settings validated and you receive a test notification email.
Validation: Click Test. If the test is successful, your PagerDuty endpoint outputs PagerDuty setting validated.
Validation: Click Test. If the test is successful, the URL you’re configuring as a notifier outputs Webhook setting validated.
Available as of v2.2.0
Validation: Click Test. If the test is successful, you should receive an alert message.
Available as of v2.4.6
Validation: Click Test. If the test is successful, the DingTalk notifier output is DingTalk setting validated.
Validation: Click Test. If the test is successful, the Teams notifier output is MicrosoftTeams setting validated.
After you set up notifiers, you can manage them. From the Global view, open the cluster that you want to manage your notifiers. Select Tools > Notifiers. You can:
{ "receiver": "c-2a3bc:kube-components-alert", "status": "firing", "alerts": [ { "status": "firing", "labels": { "alert_name": "Scheduler is unavailable", "alert_type": "systemService", "cluster_name": "mycluster (ID: c-2a3bc)", "component_name": "scheduler", "group_id": "c-2a3bc:kube-components-alert", "logs": "Get http://127.0.0.1:10251/healthz: dial tcp 127.0.0.1:10251: connect: connection refused", "rule_id": "c-2a3bc:kube-components-alert_scheduler-system-service", "severity": "critical" }, "annotations": {}, "startsAt": "2020-01-30T19:18:13.321684733Z", "endsAt": "0001-01-01T00:00:00Z", "generatorURL": "" } ], "groupLabels": { "component_name": "scheduler", "rule_id": "c-2a3bc:kube-components-alert_scheduler-system-service" }, "commonLabels": { "alert_name": "Scheduler is unavailable", "alert_type": "systemService", "cluster_name": "mycluster (ID: c-2a3bc)" } }
After creating a notifier, set up alerts to receive notifications of Rancher system events.