Alert Channels

Email alerts are built into every Monitorion account with no external service required. Alerts are sent via Monitorion's own transactional email infrastructure and arrive within seconds of an incident being confirmed.

Setup

1. 1Go to Settings > Notifications.
2. 2Under Email Alerts, verify the address shown or add an additional recipient.
3. 3Click Send test alert to confirm delivery.

What the email contains

• Monitor name and URL / host
• Current status (Down / Degraded / Recovered)
• Time of first failure and duration
• Error message or HTTP status code
• Direct link to the monitor detail page

SMS alerts are delivered internationally SMS carriers, with coverage in 180+ countries. International numbers in E.164 format (e.g. +447911123456) are fully supported. No third-party account needed.

Setup

1. 1Go to Settings → Notifications.
2. 2Enter your phone number in E.164 format (e.g. +306981234567).
3. 3Enable the SMS alerts toggle.
4. 4Optionally adjust your repeat alert interval to control how often SMS fires for an ongoing incident.

Example message

🚨 Monitorion: api.acme.com is DOWN — Connection timeout after 30s

✅ Monitorion: api.acme.com is back UP

Monthly allocation per plan

SMS credits are additional messages you can purchase on top of your monthly plan allocation. Credits never expire and are used automatically when your monthly allocation runs out.

Credit packs

How to buy credits

1. 1Go to Settings → Notifications.
2. 2In the SMS section, scroll to Top up with extra SMS credits.
3. 3Click a credit pack — you'll be taken to a secure checkout.
4. 4After payment, credits are added to your balance instantly and shown in the SMS section.

How credits are used

Viewing your balance

Your current credit balance and monthly usage are shown in Settings → Notifications → SMS Alerts. The usage bar shows plan SMS used this month; the blue card shows remaining purchased credits.

Infrastructure

SMS supports international delivery. Rates vary by country. You do not pay per-message directly — Monitorion absorbs the cost within your plan allocation and credit purchases.

Slack alerts post rich-formatted messages to any channel. The message includes the monitor name, current status, error detail, and a button linking directly to the monitor detail page.

Setup

1. 1In your Slack workspace, go to Apps > Incoming Webhooks (or create a new Slack app at api.slack.com/apps).
2. 2Enable Incoming Webhooks, click Add New Webhook to Workspace, and choose the target channel.
3. 3Copy the webhook URL (starts with https://hooks.slack.com/services/).
4. 4In Monitorion, go to Project Settings > Alert Channels > Add Channel > Slack, paste the URL, and click Save.
5. 5Click Send test alert to verify the message arrives.

Example payload sent to Slack

{
  "text": "🔴 Monitor alert from Monitorion",
  "attachments": [
    {
      "color": "#e53e3e",
      "fields": [
        { "title": "Monitor",  "value": "api.acme.com",          "short": true },
        { "title": "Status",   "value": "DOWN",                   "short": true },
        { "title": "Error",    "value": "503 Service Unavailable","short": false },
        { "title": "Since",    "value": "2026-06-25 14:32 UTC",   "short": true }
      ],
      "actions": [
        {
          "type": "button",
          "text": "View Monitor",
          "url": "https://app.monitorion.com/monitors/abc123"
        }
      ]
    }
  ]
}

Discord alerts use Discord's native webhook API to post rich embeds with colour-coded status (red for down, green for recovered) to any server channel.

Setup

1. 1In Discord, open Server Settings > Integrations > Webhooks.
2. 2Click New Webhook, choose the target channel, and give it a name (e.g. “Monitorion Alerts”).
3. 3Click Copy Webhook URL.
4. 4In Monitorion, go to Project Settings > Alert Channels > Add Channel > Discord, paste the URL, and click Save.

Example embed payload

{
  "username": "Monitorion",
  "avatar_url": "https://app.monitorion.com/logo.svg",
  "embeds": [
    {
      "title": "🔴 Monitor Down: api.acme.com",
      "color": 15158332,
      "fields": [
        { "name": "Status",       "value": "DOWN",                    "inline": true },
        { "name": "Error",        "value": "503 Service Unavailable", "inline": true },
        { "name": "Triggered at", "value": "2026-06-25 14:32 UTC",    "inline": false },
        { "name": "Monitor URL",  "value": "https://api.acme.com",    "inline": false }
      ],
      "footer": { "text": "Monitorion" },
      "timestamp": "2026-06-25T14:32:00Z",
      "url": "https://app.monitorion.com/monitors/abc123"
    }
  ]
}

Monitorion can send alerts to any Telegram user, group, or channel via a custom bot. The bot only needs to be a member of the target chat — it does not require admin rights.

Setup

1. 1Open Telegram and start a chat with @BotFather.
2. 2Send /newbot, follow the prompts, and copy the Bot API token (looks like 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw).
3. 3Add the bot to your target group or channel. For a channel, promote the bot to admin with Post Messages permission.
4. 4To find the chat ID, send any message to the group/channel, then visit https://api.telegram.org/bot<TOKEN>/getUpdates and look for chat.id. Channel IDs start with -100.
5. 5In Monitorion, go to Project Settings > Alert Channels > Add Channel > Telegram, enter the token and chat ID, and click Save.

Example message

🔴 *ALERT — Monitor Down*

*Monitor:* api.acme.com
*Status:* DOWN
*Error:* 503 Service Unavailable
*Since:* 2026-06-25 14:32 UTC

[View Monitor](https://app.monitorion.com/monitors/abc123)

Teams alerts use Adaptive Cards posted via an incoming webhook connector. The card includes the monitor name, status, error, and a button to open the monitor.

Setup

1. 1In Microsoft Teams, right-click the target channel and select Manage channel.
2. 2Under Connectors, search for Incoming Webhook and click Configure.
3. 3Give the webhook a name and optional image, then click Create.
4. 4Copy the generated webhook URL.
5. 5In Monitorion, go to Project Settings > Alert Channels > Add Channel > Microsoft Teams, paste the URL, and click Save.

Example Adaptive Card payload

{
  "type": "message",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "type": "AdaptiveCard",
        "version": "1.4",
        "body": [
          {
            "type": "TextBlock",
            "text": "🔴 Monitor Down: api.acme.com",
            "weight": "Bolder",
            "size": "Medium",
            "color": "Attention"
          },
          {
            "type": "FactSet",
            "facts": [
              { "title": "Status",  "value": "DOWN" },
              { "title": "Error",   "value": "503 Service Unavailable" },
              { "title": "Since",   "value": "2026-06-25 14:32 UTC" },
              { "title": "Project", "value": "Acme Corp" }
            ]
          }
        ],
        "actions": [
          {
            "type": "Action.OpenUrl",
            "title": "View Monitor",
            "url": "https://app.monitorion.com/monitors/abc123"
          }
        ]
      }
    }
  ]
}

Google Chat (formerly Hangouts Chat) alerts post card messages to any Google Chat space, making them ideal for Google Workspace teams.

Setup

1. 1Open Google Chat and navigate to the target space (or create a new one).
2. 2Click the space name at the top, then select Apps & Integrations > Add webhooks.
3. 3Enter a name (e.g. “Monitorion”), optionally add an avatar URL, and click Save.
4. 4Copy the webhook URL that appears.
5. 5In Monitorion, go to Project Settings > Alert Channels > Add Channel > Google Chat, paste the URL, and click Save.

Example card payload

{
  "cardsV2": [
    {
      "cardId": "monitorion-alert",
      "card": {
        "header": {
          "title": "Monitorion Alert",
          "subtitle": "api.acme.com is DOWN",
          "imageUrl": "https://app.monitorion.com/logo.svg",
          "imageType": "CIRCLE"
        },
        "sections": [
          {
            "widgets": [
              {
                "decoratedText": {
                  "topLabel": "Status",
                  "text": "DOWN",
                  "startIcon": { "knownIcon": "DESCRIPTION" }
                }
              },
              {
                "decoratedText": {
                  "topLabel": "Error",
                  "text": "503 Service Unavailable",
                  "startIcon": { "knownIcon": "BOOKMARK" }
                }
              },
              {
                "decoratedText": {
                  "topLabel": "Since",
                  "text": "2026-06-25 14:32 UTC",
                  "startIcon": { "knownIcon": "CLOCK" }
                }
              },
              {
                "buttonList": {
                  "buttons": [
                    {
                      "text": "View Monitor",
                      "onClick": {
                        "openLink": {
                          "url": "https://app.monitorion.com/monitors/abc123"
                        }
                      }
                    }
                  ]
                }
              }
            ]
          }
        ]
      }
    }
  ]
}

The custom webhook channel POSTs a JSON payload to any URL you specify. It supports custom HTTP headers so you can authenticate with an API key, HMAC signature, or bearer token. Use it to integrate with any system that accepts HTTP callbacks — PagerDuty alternatives, internal ticketing systems, serverless functions, Zapier, Make, n8n, and more.

Setup

1. 1In Monitorion, go to Project Settings > Alert Channels > Add Channel > Webhook.
2. 2Enter the destination URL (must be publicly reachable HTTPS).
3. 3Optionally add custom headers. Common patterns:
   • Authorization: Bearer <token>
   • X-API-Key: <key>
   • X-Webhook-Secret: <shared-secret>
4. 4Click Send test payload to verify your endpoint receives and returns 2xx.

Payload shape

{
  "event":       "monitor.down",
  "triggered_at": "2026-06-25T14:32:00Z",
  "monitor": {
    "id":           "abc123",
    "name":         "api.acme.com",
    "monitor_type": "http",
    "url":          "https://api.acme.com/health",
    "project_id":   "proj_xyz"
  },
  "check": {
    "status":        "down",
    "status_code":   503,
    "response_time": null,
    "error":         "503 Service Unavailable",
    "region":        "eu-central",
    "checked_at":    "2026-06-25T14:32:00Z"
  },
  "incident": {
    "id":         "inc_789",
    "started_at": "2026-06-25T14:32:00Z",
    "duration_s": 0
  }
}

Event types

The PagerDuty integration uses the Events API v2 to create and auto-resolve incidents in your PagerDuty service. On-call schedules, escalation policies, and suppression rules configured in PagerDuty all apply automatically.

Setup

1. 1In PagerDuty, go to Services > Service Directory and open (or create) the service you want alerts routed to.
2. 2Click Integrations > Add an Integration and select Events API v2.
3. 3Copy the Integration Key (32-character string).
4. 4In Monitorion, go to Project Settings > Alert Channels > Add Channel > PagerDuty, paste the integration key, and click Save.

Trigger payload (Events API v2)

{
  "routing_key":  "YOUR_INTEGRATION_KEY",
  "event_action": "trigger",
  "dedup_key":    "monitorion-abc123",
  "payload": {
    "summary":   "[Monitorion] api.acme.com is DOWN — 503 Service Unavailable",
    "severity":  "critical",
    "source":    "api.acme.com",
    "timestamp": "2026-06-25T14:32:00Z",
    "custom_details": {
      "monitor_id":   "abc123",
      "monitor_type": "http",
      "url":          "https://api.acme.com/health",
      "status_code":  503,
      "region":       "eu-central",
      "project":      "Acme Corp"
    }
  },
  "links": [
    {
      "href": "https://app.monitorion.com/monitors/abc123",
      "text": "View in Monitorion"
    }
  ]
}

Auto-resolve payload

{
  "routing_key":  "YOUR_INTEGRATION_KEY",
  "event_action": "resolve",
  "dedup_key":    "monitorion-abc123"
}

The Jira integration automatically creates issues in your Jira Cloud project when a monitor goes down and resolves them when it recovers. Issues are created using the Jira REST API with your API token.

Setup

1. 1Generate an API token at id.atlassian.com (Atlassian Account > Security > API tokens > Create API token).
2. 2Note your Jira Cloud URL (e.g., https://yourcompany.atlassian.net).
3. 3Find your project key — the prefix in issue IDs (e.g., MON in MON-123). You can find it under Project Settings > Details in Jira.
4. 4In Monitorion, go to Settings > Notifications > Add Channel > Jira, enter your Atlassian email, API token, Jira Cloud URL, and project key, then click Save.

Nothing is worse than being woken up at 3 AM for a false alarm. Monitorion uses two layers of verification to ensure every alert represents a real problem — not a network hiccup, DNS glitch, or deploy restart.

Layer 1: Confirmation Rechecks (Single-Region)

For single-region monitors, when a check fails we don't alert immediately. Instead, we automatically run a confirmation recheck 30 seconds later. Only if the confirmation also fails do we create an incident.

• Check fails → automatic recheck queued (30-second delay)
• Confirmation also fails → incident created, alert sent
• Confirmation succeeds → transient blip ignored, no alert

Layer 2: Multi-Region Consensus (Pro+)

For multi-region monitors, every check runs from up to 5 global locations simultaneously. We use majority-vote consensus: your site is only flagged as down when 3 or more regions agree. A local network issue in one region won't trigger a false alarm. This is even stronger than confirmation rechecks.

• Check runs from 5 regions simultaneously
• Each region reports independently
• Majority (3+) must agree before creating an incident
• Alerts fire immediately on first consensus failure — no threshold needed

Consecutive Failure Threshold (Single-Region)

On top of confirmation rechecks, single-region monitors have a configurable consecutive failure threshold. This is the number of confirmed failures required before an alert fires. Go to Monitor Settings > Alert After Consecutive Failures (1–10).

Multi-region monitors don't need this setting — consensus voting already prevents false alarms, so alerts fire on the first consensus failure.

By default, Monitorion sends one alert when a monitor goes down and one when it recovers. For long-running outages you can configure a re-alert interval to receive follow-up reminders until the monitor recovers.

Setup

1. 1Go to Monitor Settings > Alert Behavior.
2. 2Enable Repeat alerts while down.
3. 3Set the Re-alert every interval. Options: 15 min, 30 min, 1 hour, 2 hours, 4 hours, 8 hours, 24 hours.

When a monitor that was previously down passes a check, Monitorion automatically sends a recovery notification across all the same channels that received the initial down alert.

What the recovery notification includes

• Monitor name and URL
• Total downtime duration (e.g. Down for 14 minutes 32 seconds)
• Time of recovery
• Link to the incident for post-mortem notes

Example Slack recovery message

{
  "attachments": [
    {
      "color": "#38a169",
      "fields": [
        { "title": "Monitor",   "value": "api.acme.com",      "short": true },
        { "title": "Status",    "value": "RECOVERED",          "short": true },
        { "title": "Downtime",  "value": "14 min 32 sec",      "short": true },
        { "title": "Recovered", "value": "2026-06-25 14:47 UTC","short": true }
      ]
    }
  ]
}

Schedule a maintenance window to suppress all alerts for one or more monitors during planned downtime — deployments, infrastructure changes, or scheduled maintenance. Checks still run and results are recorded; only alert delivery is paused.

Setup

1. 1Go to Project Settings > Maintenance Windows > Schedule Window.
2. 2Set the start and end times (your local timezone is used by default; UTC is also available).
3. 3Select the monitors to include (or choose All monitors).
4. 4Optionally set a recurring schedule (e.g. every Sunday 02:00–04:00) for regular maintenance slots.
5. 5Click Save window.

Behaviour

• Downtime during a window is excluded from uptime percentage calculations on the dashboard and SLA reports.
• If a monitor is still down when the window ends, alerts resume immediately.
• Active windows are shown with an orange badge on the monitor card.
• An optional notify before window feature can send a heads-up message to configured channels 15 minutes before the window starts.

Every alert dispatch — whether successful or failed — is recorded in the alert log. Use it to audit delivery, troubleshoot missing notifications, or verify that integrations are working correctly.

Where to find alert logs

• Per monitor: Monitor Detail page > Alert History tab. Shows every alert sent for that monitor, timestamped and with delivery status.
• Per project: Project Settings > Alert Logs. A unified feed of all alerts across all monitors and channels in the project.
• Per incident: Incident detail page > Timeline. Shows when alerts were dispatched as part of the incident timeline.

Log entry details