PagerDuty
PagerDuty tells Antimetal what paged, who owned it, and what happened last time. Antimetal connects with a read-only User API Token and uses incident history as context for root cause analysis.
What Antimetal does with PagerDuty
- Read incidents and their timelines to see what fired and how it progressed
- Look up services to map an alert to the system that owns it
- Read schedules and on-call data to know who was responsible
- Search log entries for prior occurrences of the same failure
Connecting PagerDuty
Prerequisites
- A PagerDuty account
- Permission to generate User API Tokens
In PagerDuty, click your user profile icon, then select My Profile and User Settings.
In the API Access section, click Create API User Token and follow the prompts.
Copy the token and store it securely — it will only be shown once.
Paste the token in the Antimetal UI.
Permissions and access
Antimetal connects to PagerDuty with read-only access. No write operations are performed. Antimetal reads incidents, services, schedules, on-call data, and log entries to support investigation and root cause analysis.
All tenant data is processed in isolated environments. See security and compliance for details.
Related integrations
Need help?
Contact us via Slack or at support@antimetal.com.