Pagerduty Capabilities
Last updated: October 8, 2024
After this article...
You'll understand the capabilities our Pagerduty integration provides, and how Lumos interacts with the Pagerduty API.
View users
The mapping between Pagerduty user statuses and Lumos user account statuses is below.
Pagerduty User Status | Lumos Account Status |
active (Pagerduty returns a user) | Active |
deleted (Pagerduty no longer returns a user) | Deprovisioned |
Pagerduty API endpoints:
Get all users: https://developer.pagerduty.com/api-reference/c96e889522dd6-list-users
View a user's entitlements
Lumos can retrieve the following user entitlements from Pagerduty.
Role - The Pagerduty role assigned to the employee (Manager, Admin, etc.)
Pagerduty API endpoints:
Role:
https://developer.pagerduty.com/api-reference/c96e889522dd6-list-users (we get the role from the user)
Validate on-call membership
AppStore | Offboarding | Access Reviews | License Management |
✅ | N/A | N/A | N/A |
As a condition of a pre-approval rule, Lumos can check whether a user is currently assigned to a Pagerduty on-call schedule to determine if they should be pre-approved for access to an app. see📄 Setting Up Pre-Approvals
When verifying whether a requester is part of an on-call schedule, Lumos does a real-time verification to ensure that the person receiving access is still on-call.
Pagerduty API endpoints:
https://developer.pagerduty.com/api-reference/846ecf84402bb-list-schedules
https://developer.pagerduty.com/api-reference/e1ad560792567-list-users-on-call
Deprovision a user
AppStore | Offboarding | Access Reviews | License Management |
N/A | ✅ | ✅ | ✅ |
In Lumos, deprovisioning a Pagerduty user marks their Account Status as "Deprovisioned".
In Pagerduty, this action deletes the user from your Pagerduty organization. You may run into issues deleting a user tied to existing incidents, more info can be found here: 📄 PagerDuty FAQs
This action reclaims a license in Pagerduty.
Pagerduty API endpoint: https://developer.pagerduty.com/api-reference/f99c2c2bba70b-delete-a-user
Transfer data
AppStore | Offboarding | Access Reviews | License Management |
N/A | ✅ | ❌ | ✅* |
* Available only in Inactivity Workflows
In Lumos, transferring a Pagerduty user's data to another user has no impact on their Lumos account data.
In Pagerduty, this action assigns all of the unresolved incidents and schedules that are assigned to the current user to a destination user.
Pagerduty API endpoints:
https://developer.pagerduty.com/api-reference/9d0b4b12e36f9-list-incidents (we filter to get incidents assigned to the user whose data is being transferred)
https://developer.pagerduty.com/api-reference/8a0e1aa2ec666-update-an-incident
https://developer.pagerduty.com/api-reference/846ecf84402bb-list-schedules
https://developer.pagerduty.com/api-reference/7aff39ee95bfc-update-a-schedule
https://developer.pagerduty.com/api-reference/cb747199f63a9-list-overrides
https://developer.pagerduty.com/api-reference/41d0a7c3c3a01-create-one-or-more-overrides
https://developer.pagerduty.com/api-reference/7740a1ba2d8a7-delete-an-override