Feature: PagerDuty Integration

Bidirectional.

PagerDuty webhook ingress

The PagerDuty integration lands Nova inside the on-call workflow operators already use. Webhook ingress is the entry point: PagerDuty posts incident events to Nova; the triage agent reads them and writes back its first hypothesis within 60 seconds.

• Webhook ingress. Per-service or global configuration; PagerDuty posts incident events to Nova on creation, ack, resolve.
• Triage agent on creation. Per-incident initial hypothesis posted as a PagerDuty note within 60 seconds.
• Acknowledgement participation. Per-ack contribution to MTTA; the agent’s ack is logged as a participant in the timeline.
• Per-service opt-in. Customer enables per-service; gradual rollout matches existing change-management discipline.

Acknowledgements and notes

Nova writes its actions back into the PagerDuty incident timeline. The engineer reviews; the agent never auto-applies destructive actions; the audit trail lives in PagerDuty alongside human actions.

• Status updates in timeline. Per-action timeline note in PagerDuty; matches the existing audit trail format.
• Resolution suggestions linked. Per-suggestion the linked detail; one-click apply if appropriate.
• Postmortem draft. Per-resolution auto-created PM draft; the agent does the boilerplate; the engineer writes the analysis.
• Human-in-the-loop. Destructive actions require explicit approval; the agent never restarts a service without sign-off.

Authentication

The PagerDuty integration uses scoped API keys. Rotation is supported; every action is audited on both ends; the trust boundary matches PagerDuty’s existing security model.

• API key per environment. Per-env dedicated key; staging and prod separated; blast radius bounded by environment.
• Scoped to specific actions. Acknowledge, add notes, view incidents; no incident creation or modification beyond the scope.
• Audit log. Per-action entry visible in both Nova and PagerDuty; investigation can correlate either side.
• Per-quarter key rotation. Quarterly rotation cycle; the discipline matches modern enterprise security expectations.

Rollout

The integration rolls out per service, in read-only mode first. Confidence builds before action mode; the customer’s trust accrues before the agent’s scope expands.

• Per-service enable. Customers opt in service by service; the agent’s blast radius scales with explicit consent.
• Read-only mode first. Agent observes, doesn’t act; confidence builds; promote to action mode after the watching period.
• GA across enterprise tier. Available in standard tier with limitations; enterprise tier ships full bidirectional integration.
• Per-quarter rollout review. Catches drift between intended and actual configuration; the audit keeps the integration honest.