FireHydrant Integration
Feed TigerOps AI intelligence into FireHydrant incident lifecycles, runbook tracking, and retrospectives. Complete the loop from detection to postmortem with accurate machine-generated data.
How It Works
Create a FireHydrant API Key
In FireHydrant, go to Organization Settings > API Keys and create a bot token with incident:write and retrospective:write permissions. Copy the token for TigerOps.
Configure the Integration in TigerOps
Enter your FireHydrant API token and organization slug in the TigerOps integration panel. Select which FireHydrant environments and services to map to TigerOps.
Set Up Signal Routing
Map TigerOps alert severities and service tags to FireHydrant signal rules. TigerOps can act as a signal source in FireHydrant, triggering incidents through FireHydrant native routing.
Timelines, Runbooks, and Retros Sync
TigerOps events, runbook execution results, and AI root cause data flow into FireHydrant incident timelines and retrospective templates automatically.
What You Get Out of the Box
Signal Source Integration
TigerOps integrates as a native FireHydrant signal source, so all alerts flow through FireHydrant's deduplication, routing, and on-call paging pipelines.
Incident Lifecycle Metrics
TigerOps pushes lifecycle timestamps to FireHydrant — detection time, acknowledgment time, mitigation time, and resolution time — for accurate MTTD, MTTA, MTTR tracking.
Runbook Execution Tracking
Every TigerOps AI runbook step executed during an incident is recorded as a FireHydrant incident event, providing a complete audit trail of all remediation actions taken.
Retrospective Pre-Population
TigerOps pre-fills FireHydrant retrospective templates with AI-generated contributing factors, incident timeline, impacted services, and metric charts.
Status Page Automation
When TigerOps declares a major incident, FireHydrant's native Statuspage and status site automations trigger automatically through the signal pipeline.
Follow-Up Action Tracking
Action items identified by TigerOps AI during investigation (e.g., "add circuit breaker", "increase cache TTL") are surfaced as FireHydrant follow-up tasks.
FireHydrant Lifecycle Config
Configure incident declaration, milestone mapping, and retrospective data sync.
# TigerOps — FireHydrant Integration Config
integrations:
firehydrant:
api_key: "${FIREHYDRANT_API_KEY}"
org_slug: "${FIREHYDRANT_ORG_SLUG}"
min_severity: warning
mode: "signal_source" # Options: signal_source | direct_api
auto_resolve: true
service_mappings:
- tigerops_service: "api-gateway"
firehydrant_service_id: "svc_abc123"
firehydrant_environment_id: "env_prod"
- tigerops_service: "payments-service"
firehydrant_service_id: "svc_def456"
firehydrant_environment_id: "env_prod"
milestone_mapping:
detected: "started"
acknowledged: "acknowledged"
mitigated: "mitigated"
resolved: "resolved"
retrospective:
auto_populate: true
template_id: "tmpl_xyz789"
fields:
root_cause: "{{ai_root_cause}}"
contributing_factors: "{{ai_contributing_factors}}"
timeline: "{{incident_timeline}}"
follow_up_tasks: "{{ai_action_items}}"
runbook_tracking:
enabled: true
event_type: "tigerops_runbook_executed"Common Questions
Should I use TigerOps signals or direct API integration with FireHydrant?
Using TigerOps as a FireHydrant signal source is recommended for teams already using FireHydrant's routing and on-call features — it keeps all incident orchestration within FireHydrant. The direct API mode is better if you want TigerOps to create FireHydrant incidents independently with full AI data pre-populated.
Does the integration support FireHydrant runbooks as well as TigerOps runbooks?
Yes. TigerOps can trigger FireHydrant runbook automation steps via the API when it declares an incident. Conversely, FireHydrant runbook steps can call TigerOps API endpoints. The systems are complementary — TigerOps focuses on AI diagnosis, FireHydrant on human-driven runbook workflows.
Can TigerOps data appear in FireHydrant retrospective templates?
Yes. TigerOps provides a FireHydrant retrospective data push after incident resolution, sending AI root cause analysis, incident timeline events, and metric artifacts. FireHydrant retrospective templates can reference these via custom field values.
How does TigerOps handle incidents that are declared in FireHydrant without going through TigerOps?
TigerOps can be configured to receive FireHydrant webhook events for manually declared incidents. When it detects a new FireHydrant incident for a service it monitors, TigerOps will begin investigation automatically and push its findings back to the FireHydrant incident.
Does TigerOps support FireHydrant's milestones (Detected, Acknowledged, Mitigated, Resolved)?
Yes. TigerOps maps its own incident state transitions to FireHydrant milestones. The TigerOps detection timestamp maps to Detected, first acknowledgment maps to Acknowledged, metric recovery maps to Mitigated, and full resolution maps to Resolved.
Power FireHydrant with AI Incident Data
No credit card required. Connect FireHydrant in minutes. AI data flows into every lifecycle stage.