Integrating with PagerDuty
You can send alerts to PagerDuty.
As of 28 March 2024 the IBM Log Analysis and IBM Cloud Activity Tracker services are deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to IBM Cloud Logs, which replaces these two services, prior to 30 March 2025.
Configuring PagerDuty
When you configure an alert you can have that alert sent to PagerDuty.
-
When configuring your alert, click
. -
Select if you want the alert to be sent when the condition exists (Presence) or does not exist (Absence).
-
Indicate the logging criteria when an alert should be sent. For example, when 100 lines matching in the view are logged in an hour. A graph will help you determine the number of log lines matching your specified criteria.
-
Select if the alert should be sent at the end of the selected period or immediately when the number of lines are logged.
-
Optionally you can specify a Custom schedule with alerting limited to a specified timezone, days of the week, or timeframe. To configure a Custom schedule:
- Select on for Custom schedule.
- Select the Timezone for the log entries.
- Select the days of the week when alerts should be generated.
- Optionally specify a time range for the selected days. A graph will help you determine the number of log entries for the timezone and time range.
-
Specify the Service. If required, you will be prompted to connect to PagerDuty.
If no services are listed, click Add PagerDuty to connect and add a service. Create a PagerDuty service and associate it with an escalation policy. You will be directed to PagerDuty to authorize the integration. After authorization, your alerts will display in the PagerDuty incidents dashboard.
-
Optional: You can click Test to test that your alert configuration is correct.
-
Click Save Alert.
The alert definition must be saved for alerts to be sent to PagerDuty.
Limitations
Due to PagerDuty API limitations, all requests are trimmed to a maximum of 400 KB.