PagerDuty
Audit Records
Fetches audit logs from the PagerDuty API for monitoring and analysis.
Sync Type: Incremental
Requirements
- A PagerDuty account with API access.
- An API Key to authenticate requests. Follow these steps to create one:
- Navigate to PagerDuty → Integrations → API Access Keys.
- Click Create API Key.
- Save the generated API Key securely.
Details
The PagerDuty Audit Records input retrieves audit logs from the PagerDuty API. It supports incremental sync, ensuring only new logs are fetched after the initial run. The input processes logs in paginated batches and adheres to PagerDuty's API rate limits.
Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.
Settings
| Setting | Type | Required | Description |
|---|---|---|---|
| None | - | - | No additional settings are required. |
| API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See API Rate Limiting for the field format, limits, and how to choose a value. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
| API Key | string | Yes | Token used to authenticate with the PagerDuty API. |
Connector Limitations
- This connector is restricted by PagerDuty's API rate limits.
- Ensure the API Key has sufficient permissions to access audit logs.
Troubleshooting
Common Issues
- Invalid API Key
- Error: "Authentication failed"
- Resolution: Verify the API Key is correct and has the necessary permissions.
Related Resources
Sync frequency
By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See Input Sync Frequency for details.
Last modified on