firehydrant-integration

Run the list_incidents.py script with optional filters like --status, --severity, or --environment-id. It paginates through the FireHydrant API and prints incident names, statuses, severities, and affected services, with a --json flag for structured output.

Use calculate_mttr.py with optional --severity, --service-id, and --days filters. It computes average, median, and P95 resolution times in minutes by comparing incident start times to resolved milestone timestamps.

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.

Yes, get_alert_analytics.py groups incidents by name over a date range and classifies them as noisy (more than 10 fires) or flapping (frequent with fast auto-resolution). It also reports off-hours fire rates and per-service breakdowns.

Failures typically come from API errors raised by httpx when the request returns a non-success status, or from missing authentication headers. Check that the proxy environment variables are configured and that the incident ID or date range is valid.