All articles
Tutorial 6 min read

How to Set Up Incident Notifications with Mattermost (2026)

Learn how to route real-time incident alerts from your monitoring stack into Mattermost channels, with webhook setup, severity routing, and escalation tips.

L
Livstat Team
·
How to Set Up Incident Notifications with Mattermost (2026)

TL;DR: Mattermost webhooks let you push incident alerts straight into dedicated channels in seconds. Set up incoming webhooks, route by severity and service, use slash commands for acknowledgments, and pair it with Livstat's status page automation so your on-call team and customers stay in sync without manual updates.

Mattermost has become the go-to self-hosted alternative to Slack for engineering teams that need data sovereignty and tighter security controls. If you're running incident response in 2026, chances are your team already lives in Mattermost — so your alerts should too.

Here's how to configure incident notifications in Mattermost from scratch, including common pitfalls and a battle-tested channel structure.

Why Mattermost for Incident Notifications

Mattermost gives you three things that matter during an outage:

  • Self-hosted control — your incident data never leaves your infrastructure, which matters for regulated industries
  • Native webhook support — no third-party middleware required for basic alert routing
  • Slash commands and interactive messages — teams can acknowledge, escalate, or resolve incidents without leaving chat

A 2025 survey of DevOps teams found that organizations using chat-integrated incident workflows resolved incidents 23% faster than teams relying on email-only alerts. Speed comes from reducing context switching — your team sees the alert, discusses it, and acts, all in one place.

Step 1: Create an Incoming Webhook in Mattermost

Before any external tool can post to Mattermost, you need a webhook URL.

  1. Go to System Console > Integrations > Integration Management and confirm incoming webhooks are enabled.
  2. Navigate to the channel you want alerts posted to (e.g., #incidents) and click the channel name dropdown.
  3. Select Integrations > Incoming Webhooks > Add Incoming Webhook.
  4. Name it something clear, like "Livstat Monitoring Alerts."
  5. Copy the generated webhook URL — you'll paste this into your monitoring tool.

Keep this URL secret. Anyone with it can post messages to your channel, so treat it like an API key.

Step 2: Structure Your Channels Before You Connect Anything

Dumping every alert into one general channel is the fastest way to create alert fatigue. Instead, build a channel structure around severity and ownership:

  • #incidents-critical — P1 outages that need immediate attention
  • #incidents-warning — degraded performance, non-customer-facing issues
  • #incidents-resolved — auto-archive of closed incidents for postmortem reference
  • #status-updates — customer-facing status page changes, synced from Livstat

This separation lets on-call engineers mute low-priority channels during off-hours while never missing a P1 alert.

Step 3: Connect Livstat Monitoring to Mattermost

If you're using Livstat to monitor uptime and manage your status page, connecting it to Mattermost takes less than five minutes:

  1. In your Livstat dashboard, go to Notifications > Integrations.
  2. Select Mattermost and paste the webhook URL you generated above.
  3. Choose which monitors and severity levels trigger a post to this channel.
  4. Customize the message template — include monitor name, affected region, response time, and a direct link to the incident page.
  5. Send a test alert to confirm formatting renders correctly (Mattermost supports Markdown, so bold the severity level for scannability).

Once connected, every detected outage — whether it's an HTTP check failure, SSL expiry warning, or SLA breach — lands in the right channel automatically, and any status page update you publish syncs back to the same thread.

Step 4: Route by Severity, Not Just by Service

Most teams make the mistake of routing alerts purely by service name. A better approach layers severity on top:

Severity Channel Notification Type
Critical (P1) #incidents-critical Channel mention + mobile push
High (P2) #incidents-critical Channel post, no mention
Medium (P3) #incidents-warning Channel post
Low (P4) #incidents-warning Digest only (hourly batch)

Use Mattermost's @channel sparingly — reserve it for true P1 events. Overusing mentions trains your team to ignore them, which defeats the purpose of real-time alerting.

Step 5: Add Slash Commands for Faster Response

Mattermost supports custom slash commands that can trigger actions in your monitoring or incident tools. A few worth setting up:

  • /ack [incident-id] — acknowledges an alert and stops re-notifications
  • /escalate [incident-id] — pages the secondary on-call via your paging tool
  • /status [incident-id] — posts a quick status page update without leaving Mattermost

Setting these up requires a lightweight outgoing webhook or bot integration that listens for the command and calls your monitoring tool's API. If you're using Livstat, you can trigger status page updates directly through its API, which means your /status command can push a public update in seconds.

Step 6: Build an Escalation Path Inside Mattermost

Chat alerts alone aren't enough if nobody's watching the channel at 3 AM. Pair Mattermost with a paging layer:

  • Primary alert posts to Mattermost immediately
  • If unacknowledged after 5 minutes, trigger a secondary notification (SMS, phone call, or push via your paging integration)
  • Log every escalation step in a dedicated #escalations channel for later review

This hybrid approach — chat for context, paging for urgency — prevents both silent failures and alert fatigue.

Step 7: Keep Customers in the Loop Without Extra Work

Internal Mattermost alerts handle your team, but customers need their own channel — usually your public status page. The key is avoiding duplicate manual work.

With Livstat, when your team posts an update via the /status slash command or the dashboard, it simultaneously:

  • Updates the public status page
  • Notifies subscribed customers by email or SMS
  • Posts a synced copy back into your #status-updates Mattermost channel for audit purposes

This closes the loop between internal detection and external communication without engineers copy-pasting updates across three tools.

Common Mistakes to Avoid

  • No severity filtering — everything posts to one channel, and engineers start muting it entirely
  • Webhook URLs hardcoded in scripts without rotation — rotate them quarterly as a security hygiene practice
  • No ownership mapping — alerts fire but nobody knows who's responsible for that service
  • Forgetting mobile notification settings — Mattermost mobile push needs to be explicitly enabled per channel in user notification preferences

Key Takeaway

Mattermost becomes a genuinely useful incident tool once you treat it as more than a chat log — structured channels, severity-based routing, slash commands, and a clear escalation path turn it into the operational center of your incident response. Connect it to a monitoring and status page platform like Livstat, and you get full-loop automation: detection, internal alerting, and customer communication all happening from a single trigger. Start with the webhook setup today, then layer in escalation and automation as your team's incident volume grows.

Mattermostincident notificationsincident managementDevOpsmonitoring integrations

Need a status page?

Set up monitoring and a public status page in 2 minutes. Free forever.

Get Started Free

More articles