Website monitoring alerts in Mattermost
Uptimia checks your sites, certificates and domains from 171+ locations and posts every confirmed failure into the Mattermost channel your team already uses — which site is affected, what failed and since when. No plugin, no bot account, and nothing that can read your channels.
Overview
Last 7 DaysYour server can be fine while your site is not
The containers are up, the disks are fine, and the site is still broken for the people trying to use it. An expired certificate, a DNS record that stopped resolving or a failure at the edge only shows up when something checks the way a visitor does — from outside your network.
Every graph says healthy
The app is running and the containers are happy. From inside the network an expired certificate simply doesn’t exist — the browser warning only happens out where your visitors are.
Browsers are showing red screens
Customers don’t see your graphs — they see the browser warning and leave. The gap between those two views is exactly where outside-in monitoring lives.
One failure, handled inside Mattermost
A certificate problem takes the site down while the server itself looks fine. The alert lands in your channel, the acknowledgement and the fix happen under it, and the recovery closes the thread with the total time down.
Nothing to install, nothing to maintain
No plugin on your server, no bot account in your member list, and nothing that can read a single message in your channels. Uptimia can post to the channel you picked, and that is all it can do.
Create the incoming webhook
In Mattermost: Integrations → Incoming Webhooks → Add. Pick the channel, copy the URL, paste into Uptimia and send a test. If it’s hidden, a system admin enables webhooks in the System Console.
Route monitors to channels
Add one webhook per channel and pick the destination per monitor: outages to ~alerts, certificate and domain warnings to ~ops-warnings. Because the channel lives in the webhook, moving a feed is a change you make in Mattermost.
Set the failure mode
Decide what happens when nobody acknowledges: escalate to SMS, then to the next responder. Quiet hours and maintenance windows are honoured — a planned reboot pages no one. Escalation policies come with the Professional plan and above; the webhook itself works on every plan.
Connect Mattermost to Uptimia
Screen by screen, in the Help Center: turning on incoming webhooks in the System Console, adding the integration, and keeping the webhook URL working afterwards.
Everything you watch, one channel
A server that is up won’t tell you the domain lapsed, the certificate chain broke, or that checkout dies on step three. Every check posts into the same channel — the eight below, plus DNS, blacklist, API chains and real-user data.
Send each alert to the channel that should see it
A channel that mixes a real outage with a weekly performance report is a channel people mute. Keep the outages where they wake somebody, and send the warnings and the numbers somewhere quieter.
Watch from the outside.Alert on the inside — in your Mattermost.
Outside-in checks, alerts on your server — the full platform, 30 days free.
Behind every Mattermost post
Nothing runs on your Mattermost server and nothing new joins it. Uptimia does the watching on its own fleet and hands the results to your channels.
The dashboard when you want depth
Incidents, response times, per-region results — the drill-down behind every channel post.
171+ vantage points
Checks run from 70+ countries, and you decide how many other regions must repeat a failure before the post goes out.
Status pages included
A public status page on your own domain — for the users who ask before you’ve posted.
Uptime reports
Monthly PDFs with the numbers — straight into the SLA folder.
Response times on record
Acknowledgements are timestamped, so MTTA is measurable — not anecdotal.
When the channel isn’t enough
On an escalation policy (Professional plan and above), unacked alerts climb: SMS to the on-call, then the next person. Maintenance windows keep planned work off the pager.
How Mattermost website-monitoring alerts work
Uptimia checks your sites from 171+ locations and posts every confirmed failure into your Mattermost channel — self-hosted or Cloud, it works the same way. The message says which monitor failed, what went wrong and how urgent it is, and when the site recovers it posts again with the total time down.
An alert from inside stops at the firewall
Nothing running on your own server ever makes a request from where your customers are standing — so that is where Uptimia checks from.
External probes, internal channel
The watching happens outside your network; the conversation stays on infrastructure you own.
Exactly what arrives in your channel
Five posts cover the incident lifecycle — the channel ends up scrolling like an ops log.
See all 12 alert channels →| Post | Arrives when | Contents |
|---|---|---|
| Down alert | Backup checks confirm the failure | Monitor, cause, priority, type — plus the acknowledgement link on an escalation policy |
| Grouped digest | Monitors on one policy fail together | One post listing every monitor that is down |
| Join update | More monitors fall into the same incident | A throttled follow-up post with the new count |
| Escalation step | The alert sits unacknowledged | Climbs to SMS or another channel, then the next person |
| Recovery | The check passes again | Green bar, all-clear and total time down |
| Test post | You press Test on the integration | Proof the wiring works, before anything real |
Mattermost alerts FAQ
01Does Uptimia work with self-hosted Mattermost?+
02Do I need to install a plugin or create a bot account?+
03What does Uptimia need to reach my server?+
04What data leaves my infrastructure?+
05What can it catch that a check on our own server can’t?+
06How does acknowledging work from Mattermost?+
07Can different monitors post to different channels?+
~alerts, expiry warnings to ~ops-warnings, performance numbers to ~perf-watch.08What if nobody sees the post?+
09How noisy will the channel be?+
10Is Mattermost support an add-on?+
Add the outside view
Point Uptimia at a channel, send one test post, assign your monitors — from then on, the outside view of your site reports to your team.