Opsgenie - Create Alert

Article summary

Did you find this summary helpful?

Thank you for your feedback

Opsgenie - Create Alert creates an alert in Opsgenie for:

Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

Note:

Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.

Required Fields

These fields must be configured to run the Enforcement Set.

Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

Alert message (up to 130 characters) - Specify the message of the alert, limited to 130 characters.
Priority (required, default: P3) - Priority level of the alert. Possible values are P1, P2, P3, P4 and P5. Default value is P3.
Integrations API key - Insert a key associated with the integration in order to create alerts.

These fields are optional.

Add default incident description - Select whether to send the incident description to ServiceNow.
- If enabled, Axonius will include the default incident description (mentioned below) in the ServiceNow incident.
- If disabled, Axonius will not include the default incident description (mentioned below) in the ServiceNow incident.
Message + description example:
Alert - "test" for the following query has been triggered: Missing Sophos
Alert Details
The alert was triggered because: the number of entities is above 0
The number of devices returned by the query:4
The previous number of devices was:4
You can view the query and its results here: https://demo-latest.axonius.com/devices?view=Missing Sophos
Tags - Tags of the alert.
Alias - Client-defined identifier of the alert, that is also the key element of Alert De-Duplication.
User - Display name of the request owner.
Description - Description field of the alert that is generally used to provide a detailed information about the alert.
Note:
You can replace text with params that can assist you in better informing in the Jira Issues.
The following params can be used:
{{HOSTNAME}}, {{USERNAME}}, {{FIRST_NAME}}
Note - Additional note that will be added while creating the alert.
Source - Source field of the alert. Default value is IP address of the incoming request.

For more details about other Enforcement Actions available, see Action Library.

Was this article helpful?

Table of contents