firehydrant-integration

Query FireHydrant incidents, services, and environments to compute MTTR and alert analytics.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill firehydrant-integration-erwinv2k-tkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: firehydrant-integration
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/incidentfox/sre-agent/.claude/skills/incident-firehydrant
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill firehydrant-integration-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, and includes scripts (resource) components.

What problem does it solve? SRE teams need quick access to FireHydrant incident data for post-incident review, reliability reporting, and alert fatigue analysis without manually navigating the FireHydrant UI or writing ad-hoc API calls. ## Core Features & Use Cases - Incident Listing & Filtering: List incidents by status, severity, environment, or date range with per-incident MTTR calculation. - Incident Detail & Timeline: Retrieve full incident details including milestones, role assignments, impacted services, and timeline events. - Reliability Analytics: Calculate MTTR statistics (average, median, P95) and detect noisy or flapping alerts with off-hours fire rates. - Use Case: An SRE preparing a monthly reliability review runs the MTTR script filtered by severity and service to report resolution trends, then uses alert analytics to identify the noisiest alerts for tuning. ## Quick Start Ask the agent to list all open FireHydrant incidents and calculate the MTTR for the last 30 days.

Frequently Asked Questions about firehydrant-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list FireHydrant incidents from the command line?

Run the list_incidents.py script with optional filters for status, severity, or environment ID. It paginates through the FireHydrant incidents API and prints each incident with its status, severity, and impacted services, or outputs JSON with the --json flag.

How to calculate MTTR for FireHydrant incidents?

Use the calculate_mttr.py script with optional severity, service ID, and days parameters. It computes the time between incident start and the resolved milestone, then reports average, median, P95, fastest, and slowest resolution times.

Does the FireHydrant integration require an API key?

Credentials are injected automatically by a proxy layer, so you do not need to set FIREHYDRANT_API_KEY manually. The client also supports SANDBOX_JWT or tenant and team ID headers as fallback authentication methods.

How do I detect noisy or flapping alerts in FireHydrant?

Run get_alert_analytics.py with a since and until date range. It groups incidents by name, flags alerts firing more than 10 times as noisy and fast auto-resolving ones as flapping, and reports off-hours fire rates per alert.

What Python dependencies does the FireHydrant integration need?

The scripts require the httpx library for HTTP requests to the FireHydrant API, plus Python standard library modules like argparse, json, and datetime. All scripts share a common firehydrant_client module for authentication and requests.