Reference & migration

Migrate from OpsGenie to MonoDuty

Migrate Opsgenie senders to the MonoDuty Webhook by mapping payloads to the native JSON contract and testing retries before cutover.

Migrate from Opsgenie with an explicit transform

MonoDuty does not currently expose a drop-in Opsgenie Alert API v2 endpoint. Inventory each sender and transform its payload to the native MonoDuty Webhook contract before a controlled parallel run.

Target endpoint and field mapping

POST https://mndty.com/YOUR_WEBHOOK_TOKEN

Opsgenie field	MonoDuty field	Transform
`message`	`title` or `message`	Required output
`alias`	`Idempotency-Key`	Send as a header
`description`	`description`	Direct string mapping
`priority`	`severity`	Explicitly map P1–P5 to CRITICAL/HIGH/MEDIUM/LOW
`source`	`source`	Direct string mapping
`details`	`metadata`	Bound and sanitize before sending

Controlled migration

Create the target workspace, teams, services, schedules, and escalation policies.
Create an explicit Webhook source for each owned service.
Add a sender-side transform to the native MonoDuty fields.
Run Opsgenie and MonoDuty in parallel with representative create and recovery scenarios.
Cut over in batches only after incident ownership and delivery match.

A URL-only replacement is not supported.

Transformed request example

curl -X POST https://mndty.com/YOUR_WEBHOOK_TOKEN   -H "Content-Type: application/json"   -H "Idempotency-Key: db-replication-lag-prod"   -d '{
    "title":"Database replication lag exceeding threshold",
    "severity":"HIGH",
    "description":"Replica lag exceeded 30 seconds",
    "source":"opsgenie-migration-adapter",
    "metadata":{"cluster":"prod-mysql-01"}
  }'

Retry the exact request to verify HTTP 200 with duplicate: true. Change the body without changing the key to verify HTTP 409 before production cutover.