Contact Points

To manage contact points, click the Alerts tab, and select Contact points sub-menu.

The Contact points interface appears.

Contact points interface

1. Selectors are for bulk actions, such as Delete.
2. List of all alerts in the system.

Includes:

1. Selectors for bulk actions
2. Contact point name that you define when you Add a contact point
3. Type of contact point you choose when you Add a contact point

The options are:

• (Email)
• (PagerDuty)
• (Slack)
• (Microsoft Teams)
• (Webhook)
• (Google Chat)
• (OpsGenie)

3. For specific contact points, hover over the table row, and:
4. Click (Edit) to change the definition of an existing contact point.
5. Click (Delete) to remove the contact point from the system; see Delete contact point.

Add a contact point

To add a new contact point, follow these steps:

1. Click (Add New Contact Point).

2. The Create Contact points interface appears.

3. Start by specifying the Contact point name.

4. [Optional] Specify Choose mute timing from the drop-down; see Schedule Alert Suppression for details.

5. Choose contact point type.

By default, the contact point is an Email. The other options are PagerDuty, Slack, Microsoft Teams, Webhook, Google Chat, and OpsGenie.

6. Depending on the contact point type, specify the settings.

To format subject, body of message, and similar fields, you can use the GO Templating Language.

Required field:

• Addresses: Use one or more email addresses.

Optional fields:

• Single email: Select to have all recipients on the To line.
• Message: Plain text, or format with GO Templating Language.
• Subject: Plain text, or format with GO Templating Language.

PagerDuty

Required field:

• Integration Key: This is the PagerDuty integration key for your account.

Optional fields:

• Severity: Severity of the event: critical (default), error, warning, or info.
• Class: The class or type of event, such as "cpu load", "ping failure", and so on.
• Component: Component of the source responsible for the event, such as "mysql", "eth0", and so on.
• Group: Logical grouping of service component, such as "app-stack".
• Summary: Summarize content.
• Source: Location of the affected system, such as hostname or FQDN.
• Client: Monitoring client that triggers this event.
• Client URL: URL of the monitoring client.
• Details: A set of key/value pairs that provide further details about the incident.

Slack

Required fields:

• To authenticate, use either a combination of Recipient and Token, or the Webhook URL.

Optional fields:

• Username: Username for the bot’s message.
• Icon emoji: An emoji icon for the bot’s message.
• Icon URL: URL to image source icon for the bot’s message.
• Mention Users: One or more users, in a comma-separated list, to notify in a channel, by ID.
• Mention Groups: One or more groups, in a comma-separated list, to notify in a channel, by ID.
• Mention Channel: Select one of the options from the drop-down: Disabled, Every active channel member, Every channel member.

Microsoft Teams

Required field:

• URL: Teams incoming webhook URL.

Webhook

Required field:

• URL: The URL of the alert.

Optional fields:

• HTTP Method: Choose one of: POST, PUT.
• HTTP Basic Authentication - Username: Username for basic HTTP authentication.
• HTTP Basic Authentication - Password: Password for basic HTTP authentication.
• Authorization Header - Scheme: Scheme for the authorization request header.
• Authorization Header - Credentials: Credentials for the authorization request header.
• Max Alerts: Maximum number of alerts to include in a notification.
• Title: Templated title of the message.
• Message: Custom message.

Google Chat

Required field:

• URL: Google Chat incoming webhook URL.

Optional fields:

• Title: Templated title of the message.
• Message: Body of the message.

OpsGenie

Required fields:

• API Key: OpsGenie API key.
• Alert API URL: The URL of the alerts, such as https://api.opsgenie.com/v2/alerts.

Optional fields:

• Message: Alert text; can be plain text, or use format templates.
• Description: Description of the incident.
• Auto close incidents: When selected, automatically closes alerts in OpsGenie after alert status returns to ok.
• Override priority: When selected, enables the user to set alert priority using og_priority annotation.
• Send notification tags as: Sends the common annotations to OpsGenie as Tags, Extra Properties, or Tags & Extra Properties.

6. Click (Test) to validate the configuration of the contact point.
7. Finalize the configuration by clicking (Save contact point).

Add another configuration to the contact point

Organizations often have several communication methods, so you can establish multiple contact point types.

1. Click (Add another) to begin configuring another contact point, as described above.
2. Click (Test) to ensure that the contact point works.
3. Click (Save contact point).
4. Optional: A (Delete) option appears for each contact point definition.

Delete contact point

When you click Delete, confirm your action in the Delete Contact Point confirmation dialog by clicking .