Analytics
Connect Pagerduty to DataxLand
The PagerDuty connector reads incidents, incident logs, services, teams, users and the list of priority levels. Si maps incidents to the incident entity of the IT model, so you get incident counts, P1 incidents, resolved incidents and mean time to resolve by service; for online stores, add your orders to estimate the revenue affected when a service is down, using the pack's exact definition.
Free plan with no time limit · No card required · Sample workspace ready in minutes
What you can do with Pagerduty
- Track MTTR by service and by month.
- Post a weekly count of P1 incidents to the operations team's Slack channel.
- Put incidents next to hourly revenue to see the impact on sales.
What data you get
Each stream lands as its own table in the workspace warehouse, as is; personal-data columns are hashed on load.
| Stream (table) | Contents |
|---|---|
| incidents | Incidents with service, urgency, priority, status, opened and resolved times. |
| incident_logs | Log of each handling step (alert, acknowledge, resolve). |
| services | Monitored services. |
| teams | On-call teams. |
| users | On-call users; emails are hashed on load. |
| priorities | The list of priority levels (P1, P2...). |
Connection details
| Sign-in method | Connection details (API key, account), encrypted at rest |
|---|---|
| Sync modes | Full (reloaded each run) |
| Fields to fill in | API key |
| Developer | Airbyte (community), run inside DataxLand |
| License | ELv2 |
Passwords and keys are encrypted at rest. Personal-data columns are hashed on load.
Metrics computed from this source
Real definitions from the analytics packs; dashboards and Si share them.
| Metric | Definition | Unit |
|---|---|---|
| Incidents | Number of incident-type tickets opened in the period, by open date. | Count |
| P1 incidents | Number of highest-priority incidents (P1, critical) opened in the period. | Count |
| Resolved incidents | Number of incidents resolved in the period, by resolution date. | Count |
| Mean time to resolve (MTTR, hours) | Average hours from open to resolution for incidents resolved in the period.= it_incident_hours_total / Resolved incidents | Number |
Connect Pagerduty in 3 steps
- 1
Create an API key
In PagerDuty, go to Integrations → API Access Keys and create a read-only key.
- 2
Add the PagerDuty source
In the workspace choose Add source, find PagerDuty and paste the API key; you can set how many days to re-read (Cutoff Days) and exclude services.
- 3
Choose streams and review
Click Test connection, select incidents, services and priorities; Si proposes an incident mapping for you to approve before the build.
Limits and caveats
- Streams reload everything within the configured date range on each refresh; keep that range only as large as you need.
- P1 is based on your account's priority list; if you do not use priorities, choose urgency as a substitute at the review step.
- Requires the Starter plan or above. A community Airbyte connector (ELv2) run inside DataxLand.
Frequently asked questions
Can it compute service availability?
The availability metric needs outage minutes and planned time; PagerDuty provides incident open and close times, and you supply the planned time separately in Excel.
Can I acknowledge or resolve incidents from DataxLand?
No. The connector is read-only.
How often does it refresh?
On the schedule you set, as often as hourly on the Starter plan.
Dashboard templates that use this source
Connect Pagerduty and get verified dashboards
Free plan with no time limit · No card required · Sample workspace ready in minutes