Hands-on tutorial

Tutorials · Monitoring

How to Monitor Services and Publish a Status Page

Check websites, VPNs, portals and internet links from outside every minute, alert the team when they fail, and keep users informed with a simple status page.

Beginner8 min7 steps

Before you start

  • A small server or container host (ideally outside your main site)
  • The list of services and their URLs or addresses
  • An alert destination: email, chat or ticketing

Step by step

  1. Choose what users experience

    Monitor the things users notice: the website, customer portal, VPN gateway, email, Wi-Fi portal and each site's internet link.

  2. Run checks from outside

    Host the monitor in the cloud or at another site, so it still works and reports when your main site is down.

  3. Deploy a monitoring tool

    Open-source tools such as Uptime Kuma run in one container and support HTTP, TCP, ping, DNS and certificate checks.

    docker run -d --restart=always -p 3001:3001 -v uptime:/app/data --name uptime louislam/uptime-kuma:1
    
  4. Add checks and thresholds

    Check every 60 seconds, alert after 2–3 failed checks to avoid false alarms, and monitor TLS certificate expiry.

  5. Connect alerts

    Send alerts to the team channel and ticketing, with escalation if nobody acknowledges.

  6. Publish a status page

    Create a public or internal page with the main services, so users and managers can see current status without calling the helpdesk.

  7. Post incident updates

    During an outage, post short updates: what is affected, what you are doing, and when the next update will come.

Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.

Pro tips

  • Protect the monitoring dashboard with strong authentication.
  • Don't expose internal details on a public status page.
  • Use monthly uptime figures in management reports.