opsgenie-integration

Query Opsgenie alerts, on-call schedules, and compute MTTA/MTTR metrics via Python scripts.

656|82|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/incidentfox/incidentfox --skill opsgenie-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsgenie-integration
Source: https://github.com/incidentfox/incidentfox/tree/main/sre-agent/.claude/skills/alerting-opsgenie
Command: npx skills add https://github.com/incidentfox/incidentfox --skill opsgenie-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

On-call engineers and SREs need fast access to Opsgenie alert data, on-call schedules, and reliability metrics without manually navigating the Opsgenie UI or writing ad-hoc API calls. This Skill provides ready-to-run scripts for alert triage, on-call lookups, and alert fatigue analysis.

Core Features & Use Cases

  • Alert Management: List, filter, and inspect Opsgenie alerts by status, priority, team, or custom query, including full alert timelines via log entries.
  • On-Call Scheduling: Look up current on-call participants by schedule or team, and list teams and services.
  • Reliability Metrics: Compute MTTA/MTTR statistics over date ranges and run alert fatigue analysis that classifies noisy and flapping alerts with acknowledgment and off-hours rates.
  • Use Case: During an incident review, run the analytics script over the past month to identify the noisiest alerts with low acknowledgment rates, then check MTTR by priority to report on team response performance.

Quick Start

Ask the AI to list all open P1 alerts in Opsgenie and show who is currently on call for the affected team.

Frequently Asked Questions about opsgenie-integration

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

FAQPage Schema
How do I list open Opsgenie alerts from the command line?

Run list_alerts.py with the --status open flag to fetch open alerts via the Opsgenie v2 alerts API. You can add --priority P1 or a custom --query to narrow results, and --json for machine-readable output.

How to check who is on call in Opsgenie?

Use get_on_call.py with a --schedule-id or --team-id to see current on-call participants. Without arguments, it iterates all schedules and reports on-call users for each.

How do I calculate MTTR for Opsgenie alerts?

Run calculate_mttr.py with optional --team-id, --priority, and --days filters. It queries closed alerts in the period and reports average, median, P95, fastest, and slowest resolution times in minutes.

Do I need to set the OPSGENIE_API_KEY environment variable?

No. Credentials are injected automatically by a proxy layer, so the scripts work without OPSGENIE_API_KEY visible in the environment. You can optionally set OPSGENIE_BASE_URL or OPSGENIE_API_URL to override the API endpoint.

What is alert fatigue analysis and how does it detect noisy alerts?

The get_alert_analytics.py script groups alerts by message over a date range and computes fire count, acknowledgment rate, MTTA, MTTR, and off-hours rate. Alerts with more than 10 fires and under 50% acknowledgment are classified as noisy, and high-frequency alerts resolving in under 10 minutes are flagged as flapping.