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.
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
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.
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.
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:1Add checks and thresholds
Check every 60 seconds, alert after 2–3 failed checks to avoid false alarms, and monitor TLS certificate expiry.
Connect alerts
Send alerts to the team channel and ticketing, with escalation if nobody acknowledges.
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.
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.
FAQ
Frequently asked questions
Is this the same as network monitoring?
No. Network monitoring watches devices; uptime monitoring checks services the way users experience them. Use both.
How often should checks run?
Every 30–60 seconds for important services is common.
Keep learning
Related guides
Network alerts by email and webhook
Read more →What is a NOC?
Read more →Network KPIs and SLA reporting
Read more →How to Monitor Your Network With SNMP and Syslog
Know about failures before users call: collect interface statistics with SNMPv3 and central logs with syslog.
Read more →How to Synchronise Time on Network Devices With NTP
Accurate clocks are essential for logs, certificates, schedules and CCTV evidence. Configure NTP everywhere in minutes.
Read more →How to Back Up and Restore Network Device Configurations
A configuration backup turns a failed device into a quick swap. Set up regular backups and test a restore.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.