Skip to content
Reoclo Reoclo Reoclo Docs

OpsGenie Notifications

Reoclo creates OpsGenie alerts via the Alerts API v2, with per-channel region selection (US or EU), optional team routing, and a customizable severity → priority map.

When to use it

Section titled “When to use it”
  • Your on-call lives in OpsGenie’s rotations and policies
  • You want alerts routed to specific teams without touching escalation policies in Reoclo
  • You use Jira Service Management — OpsGenie alerts integrate natively

For PagerDuty, see PagerDuty. For chat, see Slack or Microsoft Teams.

Prerequisites

Section titled “Prerequisites”
  • An OpsGenie account (US or EU data residency)
  • Permission to create API integrations
  • (Optional) The name of an OpsGenie team you want alerts assigned to

Step 1 — Create an API integration

Section titled “Step 1 — Create an API integration”
  1. In OpsGenie, open Settings → Integrations (or Teams → <your team> → Integrations if you want the integration scoped to one team).
  2. Click Add Integration and pick API.
  3. Name it (e.g., Reoclo).
  4. Copy the API Key. It’s a UUID-formatted string.
  5. Make sure Enabled is on and Create and Update Access is granted.
  6. Click Save Integration.

Note your region:

  • US accounts use api.opsgenie.com
  • EU accounts use api.eu.opsgenie.com

Reoclo picks the right host from the region you set on the channel.

Step 2 — Create the channel in Reoclo

Section titled “Step 2 — Create the channel in Reoclo”

Dashboard

Section titled “Dashboard”
  1. Open Settings → Notification Channels.
  2. Click Add Channel → OpsGenie.
  3. Give it a name (e.g., oncall-platform).
  4. Pick the Region — us or eu. This must match your OpsGenie account.
  5. (Optional) Enter a Team name to auto-assign new alerts to that team’s responders.
  6. Paste the API Key into API Key.
  7. (Optional) Customize the Priority Map — see below.
  8. Click Send Test — a [TEST] Reoclo notification channel test alert should appear in OpsGenie with priority P5.
  9. Pick which events this channel receives.
  10. Save.
  11. Close or acknowledge the test alert so your rotation isn’t disturbed.

CLI

Section titled “CLI”
Terminal window
reoclo channels create opsgenie \
  --name "oncall-platform" \
  --config region=us,team=platform \
  --secret "<your-api-key>" \
  --events deploy_failed,monitoring_uptime_down,incident_created

Or via YAML with a custom priority map:

kind: opsgenie
name: oncall-platform
config:
  region: us
  team: platform
  priority_map:
    critical: P1
    warn: P2
    info: P4
secret: ${env:OPSGENIE_API_KEY}
events:
  deploy_failed: true
  monitoring_uptime_down: true
  incident_created: true
  security_ip_conflict: true

Priority mapping

Section titled “Priority mapping”

Reoclo carries one of three severities into OpsGenie’s priority field:

Reoclo severityDefault OpsGenie priority
criticalP1
warnP3
infoP5
noneP5

Override per-channel via priority_map:

config:
  region: us
  priority_map:
    critical: P1
    warn: P2
    info: P4

Valid priorities are P1 through P5. P1 typically pages immediately; P5 rarely notifies — pick whatever matches your existing escalation policies.

Payload

Section titled “Payload”

Reoclo posts to https://api.opsgenie.com/v2/alerts (or the EU host) with header Authorization: GenieKey <api-key>:

{
  "message": "Deployment failed",
  "description": "Deployment of MyApp to prod-1 failed: exit code 137 (OOM)",
  "priority": "P1",
  "source": "reoclo",
  "details": {
    "test": "False",
    "deployment_id": "dep-abc123",
    "application_name": "MyApp"
  },
  "responders": [{ "name": "platform", "type": "team" }]
}

The responders array is included only when you set a team in the channel config. OpsGenie returns 202 Accepted on success.

Troubleshooting

Section titled “Troubleshooting”
SymptomCauseFix
401 UnauthorizedWrong key or pointed at the wrong regionVerify the API key and that region matches your OpsGenie account (us vs eu)
403 ForbiddenAPI integration missing Create and Update AccessEdit the integration in OpsGenie and grant the permission
422 team does not existTeam name in config doesn’t match an OpsGenie teamFix the team value in the channel config to match the team name exactly
Alerts assigned to no oneteam config left blankAdd a team to route, or configure OpsGenie alert policies based on the source: reoclo tag
Test passes, real events silentEvent toggles disabledOpen the channel and enable the events you want

Routing tips

Section titled “Routing tips”
  • Scope integrations to teams. Creating the integration inside a team in OpsGenie automatically sets that team as the default responder and is cleaner than setting team per-channel in Reoclo.
  • Use multiple channels for multiple teams. Create one Reoclo channel per OpsGenie team and filter events to what each team should own.
  • Pair with chat. Page via OpsGenie, but also broadcast to a Slack channel so the team has shared context.

Next Steps

Section titled “Next Steps”