Send monitor failures, recovery events, incidents, and maintenance notices.
Integration · Integrations
PagerDuty alerts for FTStatus
Route FTStatus monitor events to PagerDuty when that channel is configured for your workspace.
HTTPDNSSSLAPI
Reliable visibility without exposing internal infrastructure.
Use test notifications before relying on an alert route.
Keep credentials redacted and scoped to the workspace.
Watch the signal
Track the public evidence customers actually experience.
Measure the trend
Keep response, uptime, and incident context close to the decision.
Route the response
Alert the right people and publish customer-safe updates when needed.
Events supported
Use integrations for monitor failure, degraded state, recovery, incident updates, and scheduled maintenance where the channel supports them.
Setup approach
Create the channel, validate the destination, send a test notification, then attach it to the monitors or pages that need it.
Operational caution
Do not advertise an integration publicly until credentials, test-send, and failure behavior are verified in staging.
Setup workflow
From first check to customer-ready status.
Create the PagerDuty destination.
Send a test notification.
Attach the route to selected monitors or incidents.
Validate
Test the destination before relying on it.
Attach
Choose the monitors or incidents that should notify.
Audit
Keep credentials redacted and errors observable.
Related pages
Continue building the monitoring workflow.
Ready to set up the right monitors?
Start with critical customer-facing services, then add status pages, alert routes, and managed help as reliability becomes more important.