Actions for PagerDuty #
- Send Data to PagerDuty. Sends a custom set of Lucidum data to PagerDuty.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to PagerDuty on a regular schedule.
- You can send normalized, enriched Lucidum data to PagerDuty to be indexed, searched, and analyzed.
Prerequisites #
To execute PagerDuty actions, you must:
-
Configure a user account in PagerDuty that has API permissions. The required parameters are described in the instructions for creating a Lucidum Connector for PagerDuty. For details, see https://lucidum.io/docs/pagerduty/.
NOTE. The specified account should have read and write permissions.
Workflows #
- Creating a new Configuration and a new Action
- Cloning an Existing Action
- Creating a new Action from the Location Results page
- Editing a Configuration
- Editing an Action
- Viewing Information about an Action
PagerDuty Configuration #
To create a configuration for PagerDuty actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
-
URL. The URL for the PagerDuty API. For example, https://api.pagerduty.com/.
-
API Token. API key that has read and write access (Manager role) to PagerDuty API data. For details on API tokens, see https://developer.pagerduty.com/docs/authentication and https://support.pagerduty.com/main/docs/api-access-keys#generate-a-general-access-rest-api-key. For details on permissions, see https://support.pagerduty.com/main/docs/advanced-permissions.
-
Max # of Records per Payload. The maximum number of records to send to PagerDuty in each action. The default value is “50”.
Create a New Action #
To create an action for PagerDuty, contact Lucidum customer care.
