Statuspage Integration
Automatically open, update, and resolve Atlassian Statuspage incidents based on TigerOps detection and recovery. Keep customers informed during outages without any manual intervention.
How It Works
Generate a Statuspage API Key
In your Atlassian Statuspage dashboard, go to API Info and generate a new API key. Copy the key and your page ID — you will need both in TigerOps.
Connect Statuspage in TigerOps
Paste your Statuspage API key and page ID into the TigerOps Statuspage integration panel. TigerOps will immediately verify connectivity by listing your existing components.
Map Services to Components
Link your TigerOps monitored services to Statuspage components. When TigerOps detects an anomaly on a service, the corresponding Statuspage component status updates automatically.
Incidents Open and Resolve Automatically
TigerOps opens a new Statuspage incident with an AI-generated message when an outage is detected, and resolves it with a summary message once the service recovers.
What You Get Out of the Box
Automatic Incident Creation
TigerOps opens Statuspage incidents the moment an anomaly exceeds your configured threshold — no on-call engineer needs to manually post a status update.
AI-Generated Status Messages
Incident messages posted to Statuspage are generated by TigerOps AI — plain-language descriptions of what is impacted and what the team is investigating.
Component Status Sync
Service-to-component mapping means Statuspage component statuses (Operational, Degraded, Partial Outage, Major Outage) mirror real-time TigerOps severity levels.
Automated Resolution Updates
When TigerOps detects service recovery, the Statuspage incident is automatically resolved with a closing summary including incident duration and impacted metrics.
Incident Update Streaming
During long-running incidents, TigerOps posts periodic update messages to Statuspage as the investigation progresses — keeping subscribers continuously informed.
Subscriber Notification Control
Configure whether each TigerOps-created Statuspage incident triggers subscriber email and SMS notifications, preventing alert fatigue during minor degradations.
Statuspage Incident Automation
Map TigerOps services to Statuspage components and control incident creation thresholds.
# TigerOps — Statuspage Integration Config
integrations:
statuspage:
api_key: "${STATUSPAGE_API_KEY}"
page_id: "${STATUSPAGE_PAGE_ID}"
min_severity: critical # Only open Statuspage incidents for critical alerts
auto_resolve: true # Auto-close when TigerOps resolves
component_mappings:
- tigerops_service: "api-gateway"
statuspage_component_id: "abc123"
- tigerops_service: "payments-service"
statuspage_component_id: "def456"
- tigerops_service: "auth-service"
statuspage_component_id: "ghi789"
incident_template:
title: "{{service_name}} — {{incident_type}}"
body: |
We are investigating {{incident_type}} affecting {{service_name}}.
{{ai_summary}}
notify_subscribers: true
resolution_template:
body: |
This incident has been resolved. {{service_name}} is fully operational.
Duration: {{incident_duration}} | Root cause: {{ai_root_cause}}Common Questions
Does TigerOps support both Atlassian-hosted and self-hosted Statuspage?
TigerOps integrates with the Atlassian-hosted Statuspage via the public REST API. Self-hosted or Statuspage.io legacy instances with custom API endpoints can be configured with a custom base URL in the integration settings.
Can I prevent TigerOps from spamming Statuspage with minor alerts?
Yes. You can set a minimum severity threshold — for example, only create Statuspage incidents for critical-severity TigerOps events. Warning-level anomalies will alert your engineers via Slack or PagerDuty without touching Statuspage.
What Statuspage incident statuses does TigerOps use?
TigerOps maps to the standard Statuspage statuses: Investigating (on detection), Identified (once root cause is determined by AI), Monitoring (once metrics start recovering), and Resolved (on full recovery).
Will the Statuspage incident close automatically if TigerOps resolves the incident?
Yes. Auto-resolution is enabled by default. When TigerOps marks an incident as resolved, the Statuspage incident is closed with an AI-generated resolution message. You can disable auto-resolution and require manual closure in the integration settings.
Can I customize the message format posted to Statuspage?
Yes. TigerOps supports message templates with variables like {{service_name}}, {{incident_duration}}, {{affected_metrics}}, and {{ai_summary}}. You can write your own template or use the AI-generated default.
Automate Your Customer Status Updates
No credit card required. Connect Statuspage in minutes. Incidents open and close automatically.