--- name: opsgenie-gestion-alertas-oncall description: Configura Opsgenie para gestión centralizada de alertas, rotaciones de guardia, políticas de escalación e integración con herramientas de monitorización como Prometheus. Cubre equipos, reglas de enrutamiento, programas on-call y automatización de respuesta a incidentes. license: Apache-2.0 metadata: id: 7335e42d slug: opsgenie-gestion-alertas-oncall titulo: "Opsgenie: Gestión de Alertas y Guardias On-Call" servicio: Operaciones-PMO categoria_recurso: Automatizacion tipo: referencia nivel: avanzado idioma: es idioma_original: en acceso: gratis precio_eur: 0 plataformas: [Opsgenie, Prometheus, Alertmanager] dependencias: [OG_API_KEY, curl, jq] licencia: { spdx: Apache-2.0, redistribuible: true, uso_comercial: true } fuente: repo: TerminalSkills/skills url: https://github.com/TerminalSkills/skills/tree/main/skills/opsgenie commit: 77fa015 autor: TerminalSkills nombre_original: opsgenie duplicados_en: [] seguridad: { veredicto: seguro, riesgo: bajo, escaneado: "2026-06-14", motor: "grep-estatico+auditor-llm" } ficha: que_hace: "Configura Opsgenie para enrutar alertas, gestionar guardias on-call y escalar incidentes automáticamente." como_lo_hace: "Usa la API REST de Opsgenie v2 con curl para crear equipos, reglas de enrutamiento, programas de rotación, políticas de escalación e integraciones con Prometheus Alertmanager." content_hash: "7335e42d6c74c224bbea5ab4ad3acd3152e1ba16601376e61fb66c1d14c0d184" version: 1.0.0 --- # Opsgenie ## Overview Set up Opsgenie for centralized alert management with routing rules, on-call schedules, escalation policies, and integrations. Covers alert API, team management, notification policies, and automation. ## Instructions ### Task A: Create Teams and Routing ```bash # Create a team curl -X POST "https://api.opsgenie.com/v2/teams" \ -H "Authorization: GenieKey ${OG_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "name": "Platform Engineering", "description": "Infrastructure and platform services team", "members": [ { "user": { "username": "marta@example.com" }, "role": "admin" }, { "user": { "username": "tom@example.com" }, "role": "user" }, { "user": { "username": "nina@example.com" }, "role": "user" } ] }' ``` ```bash # Create a routing rule for the team curl -X POST "https://api.opsgenie.com/v2/teams/Platform%20Engineering/routing-rules" \ -H "Authorization: GenieKey ${OG_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "name": "Critical Production Alerts", "order": 0, "criteria": { "type": "match-all-conditions", "conditions": [ { "field": "priority", "operation": "equals", "expectedValue": "P1" }, { "field": "tags", "operation": "contains", "expectedValue": "production" } ] }, "notify": { "type": "escalation", "name": "Platform Critical Escalation" }, "timezone": "America/New_York" }' ``` ### Task B: Create Alerts ```bash # Create an alert curl -X POST "https://api.opsgenie.com/v2/alerts" \ -H "Authorization: GenieKey ${OG_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "message": "Payment Service: Error rate exceeded 5%", "alias": "payment-service-error-rate-prod", "description": "Error rate for payment-service in production has exceeded the 5% threshold. Current rate: 8.3%.\n\nAffected endpoints: /api/charge, /api/refund\nDashboard: https://grafana.internal/d/payments", "responders": [ { "name": "Platform Engineering", "type": "team" } ], "tags": ["production", "payment", "critical"], "priority": "P1", "entity": "payment-service", "source": "prometheus-alertmanager", "details": { "error_rate": "8.3%", "threshold": "5%", "runbook": "https://wiki.internal/runbooks/payment-errors" } }' ``` ```bash # Acknowledge an alert curl -X POST "https://api.opsgenie.com/v2/alerts/payment-service-error-rate-prod/acknowledge?identifierType=alias" \ -H "Authorization: GenieKey ${OG_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "user": "marta@example.com", "note": "Investigating — checking database connections." }' ``` ```bash # Close an alert curl -X POST "https://api.opsgenie.com/v2/alerts/payment-service-error-rate-prod/close?identifierType=alias" \ -H "Authorization: GenieKey ${OG_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "user": "marta@example.com", "note": "Fixed connection pool sizing. Error rate back to normal." }' ``` ### Task C: On-Call Schedules ```bash # Create an on-call schedule with weekly rotation curl -X POST "https://api.opsgenie.com/v2/schedules" \ -H "Authorization: GenieKey ${OG_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "name": "Platform Primary On-Call", "ownerTeam": { "name": "Platform Engineering" }, "timezone": "America/New_York", "enabled": true, "rotations": [ { "name": "Weekday Rotation", "type": "weekly", "startDate": "2026-02-23T09:00:00Z", "participants": [ { "type": "user", "username": "marta@example.com" }, { "type": "user", "username": "tom@example.com" }, { "type": "user", "username": "nina@example.com" } ], "timeRestriction": { "type": "weekday-and-time-of-day", "restrictions": [ { "startDay": "monday", "startHour": 9, "startMin": 0, "endDay": "friday", "endHour": 18, "endMin": 0 } ] } } ] }' ``` ```bash # Get current on-call participants curl -s "https://api.opsgenie.com/v2/schedules/Platform%20Primary%20On-Call/on-calls" \ -H "Authorization: GenieKey ${OG_API_KEY}" | \ jq '.data.onCallParticipants[] | {name: .name, type: .type}' ``` ### Task D: Escalation Policies ```bash # Create an escalation policy curl -X POST "https://api.opsgenie.com/v2/escalations" \ -H "Authorization: GenieKey ${OG_API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "name": "Platform Critical Escalation", "ownerTeam": { "name": "Platform Engineering" }, "rules": [ { "condition": "if-not-acked", "notifyType": "default", "delay": { "timeAmount": 5 }, "recipient": { "type": "schedule", "name": "Platform Primary On-Call" } }, { "condition": "if-not-acked", "notifyType": "default", "delay": { "timeAmount": 15 }, "recipient": { "type": "user", "username": "marta@example.com" } }, { "condition": "if-not-acked", "notifyType": "all", "delay": { "timeAmount": 30 }, "recipient": { "type": "team", "name": "Platform Engineering" } } ], "repeat": { "waitInterval": 10, "count": 3, "resetRecipientStates": true } }' ``` ### Task E: Integration with Prometheus Alertmanager ```yaml # alertmanager.yml — Opsgenie receiver configuration receivers: - name: 'opsgenie-critical' opsgenie_configs: - api_key: '' message: '{{ .CommonLabels.alertname }}: {{ .CommonAnnotations.summary }}' description: '{{ .CommonAnnotations.description }}' priority: '{{ if eq .CommonLabels.severity "critical" }}P1{{ else if eq .CommonLabels.severity "warning" }}P3{{ else }}P5{{ end }}' tags: '{{ .CommonLabels.environment }},{{ .CommonLabels.service }}' entity: '{{ .CommonLabels.service }}' source: 'prometheus' responders: - name: 'Platform Engineering' type: 'team' details: alertname: '{{ .CommonLabels.alertname }}' cluster: '{{ .CommonLabels.cluster }}' ``` ## Best Practices - Use alert aliases for deduplication so the same issue doesn't create multiple alerts - Configure notification policies per user — allow P1 alerts to phone at night, P3 only during work hours - Use routing rules to direct alerts to the correct team based on tags and priority - Set escalation timeouts based on SLA requirements — shorter for P1, longer for P3 - Add runbook URLs and dashboard links in alert details for faster resolution - Use heartbeat monitoring to detect when integrations stop sending alerts