Zenduty Integration
Route TigerOps incidents through Zenduty with AI-enriched pages, on-call schedule awareness, and escalation metrics. Reduce MTTA and track on-call health across your entire team.
How It Works
Generate a Zenduty API Token
In Zenduty, navigate to Account Settings > API Tokens and generate a new token. Note your team ID and service integration keys from the Zenduty dashboard.
Create a TigerOps Alert Source in Zenduty
In Zenduty, add a new integration of type "REST API" on your target service. Copy the integration key and paste it into TigerOps alongside your API token.
Configure Service and Escalation Mappings
Map each TigerOps monitored service to a Zenduty service and escalation policy. Set which TigerOps severity levels trigger pages versus email-only notifications.
On-Call Engineers Receive AI-Enriched Pages
Zenduty pages include TigerOps AI summaries, metric values, and direct investigation links. Acknowledgment and resolution sync back to TigerOps automatically.
What You Get Out of the Box
On-Call Schedule Awareness
TigerOps reads the current Zenduty on-call schedule to display who is on-call for each service directly in the TigerOps incident view — no switching to Zenduty to check.
AI-Enriched Page Notifications
Every Zenduty page triggered by TigerOps includes the AI-generated incident summary, affected metric snapshot, and a one-click deep link to the TigerOps investigation.
Escalation Metrics Dashboard
TigerOps aggregates escalation data from Zenduty — pages sent, time to first acknowledge, escalation depth — and surfaces them in the TigerOps reliability analytics.
Bi-Directional Status Sync
Acknowledgment and resolution actions in Zenduty reflect in TigerOps incident state. TigerOps resolutions automatically send RESOLVED events to Zenduty to close incidents.
Multi-Service Routing
Route different TigerOps services to different Zenduty services and escalation policies — infrastructure to the ops service, payments to the payments service.
MTTA and MTTR Tracking
TigerOps combines its own detection timestamps with Zenduty acknowledgment timestamps to calculate and trend MTTA and MTTR per service and per on-call rotation.
Zenduty Routing Config
Map TigerOps services to Zenduty services and configure escalation policy routing.
# TigerOps — Zenduty Integration Config
integrations:
zenduty:
api_token: "${ZENDUTY_API_TOKEN}"
team_id: "${ZENDUTY_TEAM_ID}"
min_severity: warning
auto_resolve: true
sync_oncall_schedule: true
schedule_refresh_minutes: 5
service_mappings:
- tigerops_service: "api-gateway"
zenduty_service_id: "${ZENDUTY_SERVICE_API}"
integration_key: "${ZENDUTY_INTEGRATION_KEY_API}"
min_severity: critical
- tigerops_service: "payments-service"
zenduty_service_id: "${ZENDUTY_SERVICE_PAYMENTS}"
integration_key: "${ZENDUTY_INTEGRATION_KEY_PAYMENTS}"
min_severity: warning
alert_payload:
message: "{{service_name}}: {{incident_title}}"
summary: "{{ai_summary}}"
severity: "{{severity}}"
payload:
service: "{{service_name}}"
metric: "{{metric_name}}"
value: "{{metric_value}}"
trace_url: "{{trace_url}}"
dashboard_url: "{{tigerops_url}}"
inbound_webhook:
url: "https://ingest.tigerops.io/webhooks/zenduty"
events: [acknowledge, resolve, escalate]Common Questions
Does TigerOps create Zenduty incidents or just trigger alerts?
TigerOps triggers alert events on Zenduty service integrations using the Zenduty REST API. Zenduty then applies its own escalation policies and incident management workflow. Optionally, TigerOps can also create Zenduty incidents directly via the incidents API for richer pre-population.
How does TigerOps know who is on-call in Zenduty?
TigerOps calls the Zenduty on-call schedules API periodically to cache the current on-call engineer per service. This information is displayed in the TigerOps incident panel and used to auto-assign incidents in TigerOps matching on-call ownership.
Can TigerOps suppress Zenduty pages during maintenance windows?
Yes. TigerOps maintenance windows suppress all outbound notifications including Zenduty pages. If a TigerOps maintenance window is active for a service, no TRIGGER events are sent to Zenduty for that service for the duration of the window.
Is the Zenduty integration compatible with Zenduty teams and user roles?
Yes. TigerOps integrates at the service level within Zenduty, so all Zenduty team structures, user roles, and escalation policies are respected. TigerOps does not need to manage users or teams — it just sends alert events to the configured service.
Can I see Zenduty escalation data in TigerOps reports?
Yes. TigerOps receives escalation events from Zenduty via inbound webhooks and records them in the incident timeline. The TigerOps reliability report includes an on-call metrics section showing pages per week, MTTA, and escalation rate per Zenduty service.
Smarter On-Call Routing with Zenduty
No credit card required. Connect Zenduty in minutes. AI-enriched pages and schedule sync immediately.