Uptime Monitoring Setup: Complete Guide

Your site went down at 3 AM, but you only found out in the morning from an angry customer. We've faced this dozens of times, so setting up uptime monitoring is the first thing we do for any project. Without a basic HTTP check, the rest of your monitoring infrastructure is useless: you might not know about an outage until the first phone call. Recently, a client came to us: their e-commerce site was crashing every night due to a caching failure, but they had no monitoring. We deployed Uptime Kuma with a health endpoint check and identified the root cause within a day. The goal here is to cover not just the homepage but critical endpoints: API, admin panel, health endpoints, CDN. Our team has 10+ years of experience in web development and maintaining high-load projects, so we know how to set up monitoring reliably without unnecessary costs.

How to Set Up Monitoring with Uptime Kuma?

Uptime Kuma is a free self-hosted tool with a simple UI and support for multiple check types. Deploy it in minutes via Docker:

# docker-compose.yml services: uptime-kuma: image: louislam/uptime-kuma:1 volumes: - uptime-kuma:/app/data ports: - "3001:3001" restart: unless-stopped volumes: uptime-kuma: 

Supported monitor types: HTTP(S), TCP port, Ping, DNS, SSL certificate, Keyword (text presence), JSON Query, Push (heartbeat), Steam Game Server, Docker Container. For each you can set interval, retry count, and notification integrations.

Configure via UI or REST API:

# Create a monitor via API (Bearer token in Settings → API Keys) curl -X POST http://uptime-kuma:3001/api/monitor \ -H "Authorization: Bearer your_api_key" \ -H "Content-Type: application/json" \ -d '{ "name": "Main Site", "type": "http", "url": "https://example.com/", "interval": 60, "retryInterval": 30, "maxretries": 2, "keyword": "Welcome", "httpBodyEncoding": "json" }' 

Notifications: Telegram, Slack, Email, PagerDuty, Webhook, and ~90 other providers.

Which URLs to Monitor in Production?

What is a Health Endpoint and How to Implement It?

A health endpoint is a URL that returns the objective system status. We implement it in Laravel like this:

// routes/web.php Route::get('/health', function () { $checks = [ 'database' => fn() => DB::connection()->getPdo() !== null, 'cache' => fn() => Cache::store('redis')->ping(), 'queue' => fn() => \Illuminate\Support\Facades\Queue::size() < 10000, ]; $results = []; $healthy = true; foreach ($checks as $name => $check) { try { $results[$name] = $check() ? 'ok' : 'fail'; } catch (\Throwable $e) { $results[$name] = 'error: ' . $e->getMessage(); $healthy = false; } } return response()->json([ 'status' => $healthy ? 'ok' : 'degraded', 'checks' => $results, 'timestamp' => now()->toISOString(), ], $healthy ? 200 : 503); })->middleware('throttle:60,1'); 

This endpoint checks the database, Redis cache, and queue size. On deviations, it returns HTTP 503—Uptime Kuma will record the failure.

Self-hosted vs SaaS Comparison

Uptime Kuma is better for frequent checks and full control, but UptimeRobot is more convenient for a quick start. We recommend combining: Uptime Kuma for critical checks every minute and UptimeRobot as an external observer.

Why SSL Monitoring is Critical?

SSL certificate expiration is a silent disaster: browsers don't warn you, the site becomes inaccessible. Uptime Kuma has a built-in SSL Certificate monitor with an alert 14 days before expiration. Alternatively, a cron script:

#!/bin/bash DOMAIN=$1 DAYS_THRESHOLD=14 EXPIRY=$(echo | openssl s_client -connect ${DOMAIN}:443 -servername ${DOMAIN} 2>/dev/null \ | openssl x509 -noout -enddate 2>/dev/null \ | cut -d= -f2) EXPIRY_EPOCH=$(date -d "$EXPIRY" +%s) NOW_EPOCH=$(date +%s) DAYS_LEFT=$(( (EXPIRY_EPOCH - NOW_EPOCH) / 86400 )) if [ "$DAYS_LEFT" -lt "$DAYS_THRESHOLD" ]; then curl -s -X POST "https://api.telegram.org/bot$TELEGRAM_TOKEN/sendMessage" \ -d "chat_id=$CHAT_ID" \ -d "text=SSL cert for $DOMAIN expires in $DAYS_LEFT days!" fi 

Set alerts 14 days ahead—enough time to renew via Let's Encrypt or purchase a new one.

How to Set Up a Status Page?

A public status page saves you from a flood of "Is the site down?" questions. Uptime Kuma generates one out of the box—host it on a separate domain like status.example.com. You can customize the logo and colors.

What's Included in the Work

• Deploy Uptime Kuma (or SaaS alternative) tailored to your infrastructure
• Configure basic monitors (homepage, API, health, DNS, SSL)
• Connect notification channels (Telegram, Email, Slack)
• Document incident response procedures
• One training session for your team

Timelines and Cost

Basic monitoring deployment takes 2 to 4 hours, depending on complexity. A full setup with integrations and a status page takes 1–2 days. Cost is calculated individually after analyzing your project.

Our team with 10+ years of experience and over 50 successful implementations guarantees a reliable monitoring system. We don't use one-size-fits-all solutions—each project gets a custom configuration. Contact us for a consultation. Order monitoring setup and sleep peacefully.

Sources: Uptime Kuma, Wikipedia — Uptime