Opsgenie alerts for every outage
hostnag creates an Opsgenie alert on down and closes it on recovery.
Included on Business.
Down
- Action
- create
- Message
- [Critical] https://www.example.com/ is down
- Priority
- P1
- Alias
hostnag:mon-3
- Description
Down from 2 of 3 locations (US East, Frankfurt). Last error: unexpected_status: 503. Group: Client A Monitor: Marketing site Target: https://www.example.com/ Down since: 12 Sept 2026, 07:58 UTC Locations: US East, Frankfurt Status code: 503 Last error: unexpected_status: 503
Set up
- 01
Add an API integration
In Opsgenie, create an API integration and copy its key.
- 02
Pick US or EU
Match the API your Opsgenie account uses; hostnag creates an alert by alias on down and closes the same alias on recovery.
What arrives
Rendered by the same code that sends it.Back up
- Action
- close
- Alias
hostnag:mon-3
- Note
- https://www.example.com/ answered again from every location. It was down for 1 h 15 min.
Routing
Every alert follows the group's alert policy: which channels a route goes to and the minimum severity each one takes, in bands of critical, warning and info. Quiet hours hold non-critical alerts for email, Slack, Discord, SMS, Teams and Telegram until the window closes, then deliver one digest; critical alerts are never held, and webhook, PagerDuty and Opsgenie always deliver right away since they hand off to another machine, not a person. A maintenance window on a group or a monitor suppresses alerts for its duration while checks keep running. An alert nobody acknowledges escalates through up to three tiers, each after its own number of minutes, and can be acknowledged with one tap from the alert message itself.
Questions
How does hostnag avoid duplicate alerts?
Every event for the same monitor shares one alias, so a create and its close pair up automatically.
Is Opsgenie available on every plan?
No. Opsgenie is included on Business.
Watches
Add a host. Hear about it in Opsgenie.
Start free