slug: opsgenie
provider: OpsGenie
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 9
edges:
- tag: Incidents
  spec_file: opsgenie-incidents-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.9
  evidence: POST /v1/incidents/create 'Create incident', POST /v1/incidents/{identifier}/resolve 'Resolve
    incident', 'impacted services ... as part of a structured incident response workflow'
  reason: Explicit production incident lifecycle — create, close, resolve with responders and impacted
    services. Plainly Incident Response Management.
- tag: Alerts
  spec_file: opsgenie-alerts-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.85
  evidence: POST /v2/alerts/{identifier}/acknowledge 'Acknowledge alert', POST /v2/alerts/{identifier}/escalate
    'Escalate alert', POST /v2/alerts/{identifier}/assign 'Assign alert'
  reason: Operations create, acknowledge, escalate, assign and close operational alerts with responders
    (teams, users, schedules) — this is production incident detection and on-call response coordination,
    not financial-crime or marketing alerting.
- tag: Schedules
  spec_file: opsgenie-schedules-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.85
  evidence: '"The OpsGenie Schedule API enables developers to programmatically manage on-call schedules
    and rotations"; "Get schedule timeline"'
  reason: On-call schedule and rotation management is the on-call response component of Incident Response
    Management for a running service.
- tag: On Call
  spec_file: opsgenie-on-call-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.82
  evidence: GET /v2/schedules/{identifier}/on-calls 'Get on-call participants' ... 'query who is currently
    on call for a given schedule'
  reason: Resolving current on-call participants for a schedule is core on-call response tooling for the
    running service — not HR workforce scheduling.
- tag: Escalations
  spec_file: opsgenie-escalations-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: '''manage escalation policies that define how alerts are routed when initial responders do
    not acknowledge them'' ... EscalationRule'
  reason: Escalation policies route unacknowledged alerts to teams, users and schedules — configuration
    of the on-call/incident response motion. Sits under Incident Response Management; only mild ambiguity
    vs generic ITSM.
- tag: Heartbeats
  spec_file: opsgenie-heartbeats-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.78
  evidence: '''heartbeat monitors that track the health and availability of systems and services. Heartbeats
    work by expecting periodic pings ... OpsGenie generates an alert'''
  reason: Create/ping/enable heartbeat monitors is synthetic liveness monitoring of running services —
    observability of production, rather than the incident response workflow itself.
- tag: Rotations
  spec_file: opsgenie-rotations-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.78
  evidence: POST /v2/schedules/{identifier}/rotations 'Create schedule rotation' ... 'programmatically
    manage on-call schedules and rotations'
  reason: Rotation CRUD defines the on-call rota that drives alert routing and incident response; this
    is engineering on-call management, not employee shift/HR scheduling.
- tag: Overrides
  spec_file: opsgenie-overrides-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.75
  evidence: POST /v2/schedules/{identifier}/overrides 'Create schedule override'
  reason: Overrides to on-call schedules (temporary cover for responders) are part of on-call rota stewardship
    supporting incident response. Slightly indirect, hence moderate confidence.
- tag: Notification Rules
  spec_file: opsgenie-notification-rules-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.7
  evidence: '''notification rules that control how and when users receive alert notifications ... channels
    such as email, SMS, push notifications, and voice calls'''
  reason: Per-user alert notification routing is part of how on-call responders are paged during production
    incidents. Mapped to Incident Response Management, with some risk it is read as generic notification
    configuration.