PagerDuty Lite
PagerDuty is an incident response platform.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | ADDON, AUDIT_RECORD, BUSINESS_SERVICE_SUBSCRIBER_ACCOUNT, BUSINESS_SERVICE, CHANGE_EVENT, ESCALATION_POLICY, EVENT_ORCHESTRATION, EXTENSION_SCHEMA, EXTENSION, INCIDENT_WORKFLOW, LICENSE, MAINTENANCE_WINDOW, PAUSED_INCIDENT_REPORTING_ALERT, RULESET, SCHEDULE, SERVICE, TAGS, TAG_ENTITY, TEAM, TEMPLATE, USERS_HANDOFF_NOTIFICATION_RULE, USERS_NOTIFICATION_SUBSCRIPTION, USERS_SESSION, USERS, and VENDOR tables. |
| History mode | ||
| Custom data | ||
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | check | INCIDENT and LOG_ENTRIES tables. |
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Supported deployment models
We support the SaaS and Hybrid deployment models for the connector.
You must have an Enterprise or Business Critical plan to use the Hybrid Deployment model.
Setup guide
Follow our step-by-step PagerDuty setup guide to connect PagerDuty with your destination using Fivetran connectors.
Sync overview
To capture new records, we incrementally sync the following tables and their child tables:
INCIDENTLOG_ENTRIESNOTIFICATIONON_CALL
We re-import the INCIDENT table and its child tables once a week to capture updates and deletes.
We also re-import the remaining tables and their child tables during every sync to capture updates and deletes.
Schema information
This schema applies to all PagerDuty connectors.
Explore PagerDuty schema ERD