By default, AlertOps will include email integration attachments from inbound email alerts for certain types, such as documents and audio files.
You can access the attachments in the Alert Detail screen.
AlertOps will send attachments in the email notifications.
Specify a conference bridge and access code in the email mapping.
The VOIP Communication Channel will automatically insert the bridge details into the voice message, and listen for the user to press 0 to join the bridge.
Click edit button to change this text.
The Email Communication Channel will automatically insert the bridge details into the email message, and the user can click the link to dial the bridge from a smart phone.
Specify Alert Recipients in the Alert
You can send User or Group recipients in an email alert.
AlertOps will add the specified user or group as recipients.
The Recipient User must match an AlertOps username.
The Recipient Group must match an AlertOps Group name.
Link Back to the Source
Use the Source URL field to map to the alert source.
The source URL can be found on the Alert Detail screen.
Route Alerts to Different Groups
You can use filters route alerts to different users or groups.
For example, if you wanted to route incoming alerts to different teams, create an Inbound Email Integration for each team, and assign a different Recipient Group in each Integration. Configure each Integration to use the same mailbox. Next, add a unique filter to each Integration.
In this example, a body filter is used on one Email Integration to filter based on the keyword ‘Application’ appearing anywhere in the body.
Click the Add button next to the Body or Subject filter (under the Advanced tab) and enter the filter data. Use the AND constraint or NOT constraint.
Set a body filter on the second Email Integration rule to assign alerts based on another condition.
You can use Body filters and Subject filters in the same way.
Always Open a New Incident for Each Email Alert
In the Advanced Settings section, you can enable the Every Incoming Email Will Open An Alert rule.
This will force AlertOps to open a new alert each time an alert is received for the Integration.
Eliminate Duplicate Alerts
By default, AlertOps will ignore duplicate email alerts when the Advanced Mapping fields are used.
Unique alerts are identified by a combination of Source Name + Source Identifier.
When AlertOps receives an incoming alert that matches an open alert, AlertOps marks the alert as Mapped ignored.
Group Incidents Together
You can group alerts together by setting the Source Name or Source Identifier fields to use the same data.
In this example, there are two alerts created based on the initial mapping configuration.
Next, the Source Name mapping will be set to match the Identifier field mapping:
AlertOps then sees each of the alerts as belonging to the same incident.
Route Alerts to Specific Users
To send an alert to specific users, enter one or more users in the User recipients box.
Route Alerts to Specific Groups
To send an alert to specific Groups, enter one or more Groups in the Groups recipients box.
Automatically Close Alerts
By default, AlertOps will automatically close alerts when the Source Name and Source Identifier match an open alert, the CLOSE status keyword is received.
The OPEN and CLOSE status values are configured in the Advanced tab.
You can set the Status to be from the Body or the Subject.
Customize the Alert Message
By default, AlertOps will use the email subject as the alert subject and the email body as the alert message.
But you can set the Long Text and Short Text fields and use those fields instead.
To change which fields are used in the alerts, go to Communication Channel Settings.
Each Communication Channel settings gives you the option to set which field is used as the Message Text.
You can use the original message body, or the Long Text or Short Text fields.