Capabilities
| Feature | Description |
|---|---|
| Incident Monitoring | View active and resolved incidents from your dashboard |
| MTTR Tracking | Monitor mean time to resolution across services |
| Service Health | Track service status and incident frequency |
| AI Chat Integration | Query incidents, analyze patterns, and get insights via chat |
| Plan Embeds | Embed PagerDuty incidents directly in Plans for context |
| GitHub Linking | Connect GitHub commits to incidents for traceability |
| Pattern Analysis | Identify recurring incident patterns and trends |
| Business Impact Analysis | Correlate completed work with incidents to measure impact |
Connecting PagerDuty
Find PagerDuty
Scroll to the Monitoring & Incident Management section and locate the PagerDuty integration card
Start Connection
Click the PagerDuty card to open the connection page, then click Connect PagerDuty Account
Authorize Access
You’ll be redirected to PagerDuty to authorize Kasava. Review the permissions and click Allow
Kasava uses secure OAuth 2.0 authentication. Your PagerDuty credentials are never stored—only an access token for API calls.
Dashboard Incidents Card
Once connected, PagerDuty incidents appear on your main dashboard in the Incidents card. This provides at-a-glance visibility into your system health.What You’ll See
- Active incidents count (triggered + acknowledged)
- Triggered incidents with pulsing indicator for urgent attention
- Recent incidents sorted by status and time
- MTTR metrics showing average resolution time
Incident Status Colors
| Status | Indicator | Description |
|---|---|---|
| Triggered | Red pulsing icon | New incident requiring immediate attention |
| Acknowledged | Yellow clock icon | Someone is actively working on it |
| Resolved | Green checkmark | Incident has been fixed |
Urgency Levels
| Urgency | Badge | Description |
|---|---|---|
| High | Red badge | Critical, requires immediate response |
| Low | Default badge | Can be addressed during normal hours |
Support Dashboard
PagerDuty incidents also appear in the Support tab of your Product dashboard, alongside other customer support tools like Intercom and Zendesk.Accessing the Support Dashboard
- Navigate to your Product
- Click the Support tab
- Select the Incidents tab to view PagerDuty data
Support Metrics
The Support dashboard displays key PagerDuty metrics:- Active Incidents - Count of triggered and acknowledged incidents
- High Urgency - Number of high-urgency incidents requiring attention
- Resolved - Count of resolved incidents
Filtering Incidents
Use the filter buttons to focus on specific incident states:- Triggered - Show only new, unacknowledged incidents
- Resolved - Show only completed incidents
- All - Show all incidents
AI Chat Integration
Ask natural language questions about your PagerDuty data in Kasava’s AI Chat. The chat can query incidents, analyze patterns, and provide actionable insights.Example Queries
AI Capabilities
| Capability | Description |
|---|---|
| Find Incidents | Search and filter by status, urgency, service, or time |
| Analyze Patterns | Identify recurring issues and common triggers |
| Link Commits | Connect GitHub commits to incidents for traceability |
| Create Incidents | Create new incidents directly from chat |
| MTTR Analysis | Get mean time to resolution statistics |
Plan Embeds
Embed PagerDuty incidents directly in your Plans for context during planning and retrospectives.Adding an Incident to a Plan
- Open any Plan document
- Type
/pagerdutyto open the incident selector - Search for incidents by title, description, or incident number
- Click an incident to embed it
Embedded Incident Display
Embedded incidents show:- Incident number and title
- Status badge (triggered, acknowledged, resolved)
- Urgency level indicator
- Service name where the incident occurred
- Assignee if someone is working on it
- MTTR for resolved incidents
- Link to open in PagerDuty
Filtering in Selector
The incident selector supports filtering by status:- All Incidents - Show everything
- Triggered - Only new incidents
- Acknowledged - Being worked on
- Resolved - Completed incidents
Managing the Integration
Click Manage on a connected PagerDuty integration to access additional settings.Connection Status
View your connection details including:- Status - Connected or disconnected
- Subdomain - Your PagerDuty subdomain (e.g.,
yourcompany.pagerduty.com) - Last Synced - When data was last synchronized
Data Synchronization
Configure what data Kasava syncs from PagerDuty:| Option | Description |
|---|---|
| Sync Incidents | Import incident data |
| Sync Services | Import service definitions |
| Sync Users | Import user and assignee information |
| Historical Data | Number of days of history to import (1-365) |
Syncing large accounts may take several minutes. You can close the dialog and the sync will continue in the background.
Refreshing Tokens
If your connection shows issues, click the refresh button to renew your OAuth access token.Disconnecting PagerDuty
To disconnect your PagerDuty account:- Go to Settings > Integrations
- Click on the PagerDuty integration
- Click Manage
- Click Disconnect Account
- Confirm the disconnection
Linking Commits to Incidents
Connect GitHub commits to PagerDuty incidents to track which code changes resolved issues.Via AI Chat
Benefits
- Track which commits resolved incidents
- Build a history of fixes for recurring issues
- Correlate code changes with service health
Pattern Analysis
Use AI to identify patterns in your incident history:- Frequency - How often incidents occur
- Timing - Time-of-day or day-of-week patterns
- Services - Which services have the most incidents
- Resolution time - MTTR trends
- Recommendations - Suggestions for improvement
Troubleshooting
Incidents not appearing on dashboard
Incidents not appearing on dashboard
Verify that PagerDuty is connected by checking Settings > Integrations. The connection status should show your PagerDuty subdomain. If disconnected, reconnect using the OAuth flow.
Connection failed during OAuth
Connection failed during OAuth
Ensure you have sufficient permissions in your PagerDuty account to authorize third-party applications. You may need to be an Admin or Owner.
Old incidents not showing
Old incidents not showing
Check your sync settings - the Historical Data setting controls how many days of history are imported. Increase this value and trigger a sync.
MTTR not displaying
MTTR not displaying
MTTR is only calculated for resolved incidents. Active incidents won’t show resolution time until they’re resolved in PagerDuty.
Sync taking too long
Sync taking too long
Large accounts with many incidents may take time to sync. The sync continues in the background - check back in a few minutes.
Permissions
Kasava requests the following PagerDuty permissions during OAuth:| Permission | Purpose |
|---|---|
| Read incidents | Access incident data for monitoring and analysis |
| Read services | Import service definitions and status |
| Read users | Associate incidents with assignees |
| Read schedules | Access on-call schedule information |
Kasava only reads data from PagerDuty by default. The integration does not modify incidents unless you explicitly use AI chat to create incidents or link commits.
Privacy & Security
- All PagerDuty data is transmitted over encrypted connections
- OAuth tokens are stored encrypted at rest
- You can revoke access anytime from PagerDuty’s Integration settings
- Incident data is processed according to your organization’s data retention policies