On-call · Team and above (the on-call band)

Opsgenie alerts for
SSL, DNS & uptime monitoring

Create and close Opsgenie alerts from monitoring.

How it works

How Merlonix delivers to Opsgenie

Merlonix creates Opsgenie alerts through the Alerts API using your API key. Each alert carries an alias, so a re-fired alert de-duplicates to the same Opsgenie alert instead of spamming a new one, and when Merlonix sees the issue recover it closes that alert by the same alias — the alert routes into your existing Opsgenie schedules and escalation.

Alerts flow into your existing Opsgenie schedules and escalation, no separate on-call setup required.

An alias de-duplicates re-fired alerts and lets a recovery close the Opsgenie alert automatically.

If your team already lives in Opsgenie, monitoring becomes one more routed source.

Setup

Set up Opsgenie in three steps

    Step 1

    In Opsgenie, create an API integration and copy the API key.

    Step 2

    In Merlonix (Team plan or above), add an Opsgenie notification channel with the key.

    Step 3

    Send the one-click test, confirm the alert appears, then attach the channel to your assets.

What fires an alert

The delivery channel changes; the monitoring doesn’t

Every alert carries the same context regardless of destination: which client asset changed, which check fired (SSL-certificate expiry or change, DNS-record drift, domain registration/expiry, uptime, DNSSEC, security headers, blocklist status, and more), and what specifically changed. Alerts fire on real state changes between definitive checks — not on a transient blip.

Opsgenie is one of ten delivery destinations, and Merlonix also runs on-call rotations and escalation policies so the right person is paged. See alerting & on-call →

Other destinations

Prefer a different channel?

Merlonix delivers the same alerts to every destination your team already uses.

Common questions

Frequently asked questions

Which Merlonix plan includes Opsgenie alerts?

Opsgenie alert delivery is available on Team and above (the on-call band). You can start on the free plan and add Opsgenie when you are on the qualifying tier.

What do Opsgenie alerts actually contain?

Every alert carries the same context regardless of destination: which client asset changed, which check fired (SSL-certificate expiry or change, DNS-record drift, domain registration/expiry, uptime, DNSSEC, security headers, blocklist status, and more), and what specifically changed. Alerts fire on real state changes between definitive checks — not on a transient blip. The Opsgenie message carries that same context, so a responder can triage from the alert itself.

Can I use Opsgenie alongside other channels?

Yes. A single asset can send to Opsgenie and other destinations at once — for example email plus a chat channel plus an on-call channel — so no alert rides on one delivery path. Merlonix supports email, Slack, Microsoft Teams, Discord, Telegram, Google Chat, a generic webhook, SMS, PagerDuty, and Opsgenie.

Do I need access to my clients’ servers to monitor them?

No. Merlonix probes each domain from the outside in — its public SSL certificate, DNS records, registration data, and HTTP responses — the same way a browser or resolver would. You add an asset by hostname; the Opsgenie channel just decides where the resulting alert is delivered.

Wire monitoring into Opsgenie today

SSL, DNS, uptime, and vendor-aware alerts across every client asset — delivered where your team already works. Start free, no credit card.