Integrate PagerDuty Monitoring
Overview
You can configure a PagerDuty integration to automatically create events for file transfer activities and device status changes, enabling monitoring and incident response.
Once configured, whenever a selected event occurs—such as Transfer Started, Transfer Completed, Device Connected, or Device Disconnected—a corresponding event (alert or incident) is automatically created in PagerDuty.
The overall process consists of the following steps:
① Generate an Integration Key → ② Configure the Integration in the Product
Prerequisites
Before you begin, verify the following requirements.
| Item | Description |
|---|---|
| PagerDuty Account | A PagerDuty account with permission to add an Events API V2 Integration to a service. |
| Target Service | A PagerDuty service that will receive events. |
| Network | The environment where the product is installed must be able to access events.pagerduty.com over HTTPS (443). |
Generate a PagerDuty Integration Key
To send events to PagerDuty, add an Events API V2 Integration to a service and obtain its Integration Key (Routing Key).
Step 1. Add an Events API V2 Integration
In PagerDuty, navigate to Services → Service Directory, then select an existing service or create a new one.
Open the Integrations tab, click Add Integration, and select Events API V2.
Step 2. Copy the Integration Key
From the Integrations tab, copy the Integration Key (Routing Key) of the newly created integration.
Treat the Integration Key like a password. Do not expose it in public repositories or external documentation.
If the key is compromised, generate a new one from Edit Integration → Generate a new Integration Key.
Verification
✔ The Events API V2 Integration has been added.
✔ The Integration Key has been copied.
Configure the PagerDuty Integration
Enter the Integration Key into the product.
When you open the Monitoring configuration page, the following screen is displayed.
Step 1. Enter the Integration Key
Enter the generated Integration Key (Routing Key).
Step 2. Select Events
Select the events to monitor.
Multiple events can be selected. Only the selected events will generate PagerDuty events.
| Event | Trigger |
|---|---|
| Transfer Started | When a Transfer begins. |
| Transfer Completed | When a Transfer completes successfully. |
| Transfer Paused | When a Transfer is paused. |
| Transfer Recovered | When a Transfer automatically resumes after an interruption or failure. |
| Device Connected | When a device connects. |
| Device Disconnected | When a device disconnects. |
Step 3. Save the Configuration
After completing the configuration, click Add to save the integration.
Verification
✔ The Integration Key has been entered.
✔ The monitoring events have been selected.
Verify the Integration
Verify that the integration is operating correctly.
Step 1. Generate a Test Event
Start a Transfer or trigger one of the selected monitoring events.
Step 2. Verify in PagerDuty
Open the PagerDuty service associated with the Integration Key and verify that an event or incident has been created.
Verification
✔ An event has been created in PagerDuty.
✔ The generated event has been delivered successfully.
Configuration Complete
After the configuration is saved, the integration becomes active.
From this point forward, whenever one of the selected events occurs, a corresponding PagerDuty event is created automatically.
Troubleshooting
| Issue | Verification |
|---|---|
| Events are not created | Verify that the Integration Key is correct and contains no leading or trailing spaces. |
| Authentication error | Verify that the key is an Events API V2 Integration key and has not been regenerated. |
| Does not work in the EU region | Verify that EU-region accounts use the events.eu.pagerduty.com endpoint. |
| Connection failure | Verify that access to events.pagerduty.com (or the EU endpoint) over HTTPS (443) is allowed by the firewall or proxy. |