Opsgenie Actions

Actions for Opsgenie

• Create Alert. Send an alert from Lucidum to Opsgenie. Opsgenie will deliver the alert according to its policies.

Use Cases

Below are the possible use cases for the Create Alert action:

• You can create an alert from Lucidum to Opsgenie when you find zombie users (users who are using applications in your environment but are not managed in directory services). The alert can notify SecOps and IT personnel.

• You can create an alert from Lucidum to Opsgenie when you find idle AWS instances that could be retired. The alert can notify IT and Finance.

Prerequisites

Before you can execute the actions for Opsgenie, you must create an API key with write access to Opsgenie. For details, see https://support.atlassian.com/opsgenie/docs/api-key-management/.

Workflow

To create an action in Lucidum, follow these steps:

1. Choose Action Center from the left pane.

2. In the Action Center, choose from the action types in the Channels pane.

3. To create a configuration for the action, click the Manage Configuration button. A configuration provides the connection and authorization information to communicate with the external solution.

4. Save the configuration.

5. To create an action, click the Create a new action button. An action specifies the task to execute, the data to include in the action, and how frequently to execute the action.

6. Save the action.

7. Lucidum automatically executes the action at the time and recurrence you defined in the action.

You can apply an existing configuration to more than one action. If a configuration already exists, you might be able to re-use the existing configuration and might not need to create a new one.

Opsgenie Configuration

• Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

• URL. The base URL for the Opsgenie API.

• API Key. Opsgenie API key. For details, see https://support.atlassian.com/opsgenie/docs/api-key-management/.

• Host. The hostname of the Lucidum instance. For example, demo.lucidum.cloud.

• Enable SSL. Specifies whether to use SSL when connecting to the Opsgenie server. Default value is “Off”.

Create a new action/View Action

• Action Type. Select an action from the pulldown options.

• Configuration Name. Select an action configuration from the pulldown options.

• Action Name. Identifier for the action. This name will appear in the Lucidum Action Center.

• Description. Description of the action.

• Filters. For new actions, the Add Filter button leads to the New Query page, where you can query for the assets or users that the action will act upon. For existing actions, this field displays the query for this action. The Edit Filter button leads to the New Query page, with the current query already loaded for editing. For details on creating and editing queries in Lucidum, the section on Building Queries.

• Schedule Settings. Define the schedule for the action. Choices are setting a Recurrence by date and time or After Data Ingestion, which happens at least once every 24 hours and can also be triggered manually.

• Do not trigger the action unless. Specify the number of results from Filters as a prerequisite for executing the action.

• Output Fields. The fields selected for the Filters. When creating or editing the query, you can select these fields in the Query Results page > Edit Column button.

• Priority. Priority to assign to the Opsgenie alert.

• Tags. Comma-separated list of tags to include in the Opsgenie alert.

• Description. Description to include in the Opsgenie alert.

• Responder ID. ID of the responder to be notified of the alert. Can be an individual or a group.

• Responder Type. Specify the type of responder. Choices are team, user, escalation, or schedule.