Augmentt Integration: Alert Ticketing
Alert ticketing is the core of the Augmentt integration. Each time Augmentt sends an alert, the integration checks it and creates one ticket in Rev.io, usually within moments. The alert ticketing settings are on the Alert Ticketing page of the integration setup. See the Augmentt Integration: Configuration article for more information.
The integration handles each alert in the following order.
- Checks the secret value sent with the alert. An alert with a wrong or missing value is rejected.
- Reads the alert. An alert missing its ID or tenant is skipped.
- Skips the alert if it is below the Minimum Severity.
- Skips the alert if its type is on the Excluded Alert Types list.
- Skips the alert if a ticket was already created for it, so you never get two tickets for one alert.
- Finds the Rev.io customer matched to the alert's Augmentt tenant. If the tenant isn't matched, the ticket goes to the Augmentt Default customer.
- Sets the ticket priority from the alert's severity.
- Creates the ticket, with an internal note that has the full alert details.
| NOTE: Augmentt sends each alert once and never retries. Once an alert passes the secret check, the integration always tells Augmentt it was received, even if the ticket can't be created, so the alert isn't lost. Any problem creating the ticket is logged for review. |
Augmentt alerts have four severities: Informational, Low, Medium, and High. Each one becomes a Rev.io ticket priority, as shown below. You can choose a different priority for any severity in the Severity Priority Map setting, which lists your own Rev.io priorities.
| Augmentt Severity | Standard Rev.io Priority |
| High | P1 |
| Medium | P2 |
| Low | P3 |
| Informational | P4 |
A severity left blank in the setting uses the standard priority above, matched to your Rev.io priority by name. An alert with an unexpected severity is set to P1 so it still gets attention.
Two settings let you limit which alerts create tickets. Both are applied before a ticket is created, and filtered alerts are skipped without a ticket or note.
- Minimum Severity skips alerts below a severity. For example, set it to Medium and only Medium and High alerts create tickets. With Informational, every alert creates a ticket. Augmentt also has its own threshold for each alert type, so alerts you told Augmentt to ignore never reach Rev.io.
- Excluded Alert Types skips specific alert types that are too noisy, no matter their severity. Add one alert type per row, such as office365_signinfailure. The match is not case-sensitive and applies to all customers.
To find the exact alert type to exclude, open the integration's execution for one of the noisy tickets and copy the value in the alertType field.
Each alert ticket includes the following.
- Subject. Starts with Augmentt Alert: followed by the alert title. Tickets for unmatched tenants start with Augmentt Alert - Unmapped:.
- Body. The alert title, severity, Augmentt customer and tenant, affected user, when the event happened, when it was received, the alert type, the alert ID, and the description, if there is one.
- Internal note. A summary followed by every field Augmentt sent. If an alert is too long for the ticket body, the extra details move to the note so nothing is cut off.
The ticket text is plain, without special punctuation. The integration cleans each alert value so Rev.io's security checks accept it, even when a description contains brackets or parentheses.
The integration never updates or closes an existing ticket. Each alert creates its own ticket.
For more information about the Augmentt integration, see the following articles.
Augmentt Integration: Overview
Augmentt Integration: Roster Sync