Help center

9 guides written to be followed rather than skimmed. If one of them does not answer your question, that is a gap worth telling us about — hello@statuscheck.dev.

Getting started

From an empty account to a populated dashboard.

Set up StatusCheck in about fifteen minutes

The whole path: connect a vendor, watch devices arrive, group them the way you work, and turn on alerting.

Connecting your gear

Where each vendor keeps its API key, and what to paste where.

Connect Cisco Meraki

Create a Meraki Dashboard API key and paste it into StatusCheck.

Connect Ubiquiti UniFi

Create a Site Manager API key at unifi.ui.com — a console-local key will not work.

Connect Domotz

Create a Domotz Portal API key, and pick your regional API cell if the default is wrong.

Choose which sites or collectors an integration syncs

One API key often sees more than you want. The Scope picker limits what is imported, and asks what to do with devices already here.

Organizing devices

Clients, sites, floors — and how the dashboard rolls them up.

Organize devices into clients, sites and floors

Build the structure you actually work in, then assign devices to it. The dashboard rolls health up through it.

Alerting & notifications

Rules, channels, escalation and maintenance windows.

Set up alerting

Add a channel first, then a rule. Then use severities, escalation and maintenance windows to keep the volume sane.

Understanding your numbers

What uptime, availability and "degraded" actually mean here.

How uptime and availability are calculated

What the dashboard percentage measures, why a site is only "down" when everything in it is, and which number to put in front of a customer.

Troubleshooting

When an integration stops, or devices do not appear.

An integration is failing — what to do

Read the error, in order: the card status, the error list behind the count, then Test. Most causes are a rotated key or a permission change.