Alert destination

PulseTrace + Opsgenie

Open and close Opsgenie alerts automatically.

Create an Opsgenie alert when a monitor fails and close it when the monitor recovers. Alerts carry an alias derived from the monitor, so repeated failures update one alert instead of creating a pile.

Set it up in three steps

1In Opsgenie, add an API integration to the team that should be alerted and copy the API key.
2In PulseTrace, add a destination of type Opsgenie and paste the key (EU region endpoints are supported).
3Select the destination on the monitors that should alert it.

Events it receives

Monitor down / recovered
Still-down reminders
Certificate expiring
Security grade downgraded / recovered
Performance anomaly opened / closed
Significant external change (DNS, TLS, HTTP fingerprint, content)
Incident opened / acknowledged / resolved
Auto-resolve — recovery closes the open alert instead of posting a second message.

Start monitoring free Read the docs

Opsgenie alert

{
  "message": "Checkout API is DOWN",
  "alias": "pulsetrace:monitor:8f3a…",
  "priority": "P1",
  "description": "HTTP 503 from us-east, eu-west. Incident #4821.",
  "details": { "incident_url": "https://app.pulsetrace.app/dashboard/incidents/4821" }
}

Questions about Opsgenie

Does recovery close the alert?

Yes — a close request is sent for the same alias when the monitor recovers.

More alert destinations

SlackIncidents in the channel your team already watches.Microsoft TeamsAlerts in the Teams channel your team already watches.DiscordAlerts for the Discord-first team.TelegramA bot message the moment something drifts.PagerDutyTrigger and auto-resolve PagerDuty incidents.incident.ioDeclare incidents in incident.io from monitor failures.