Server Monitoring

Your Server Stopped Reporting.
But Is Everything Actually OK?

Your monitoring agent crashed. Your cron job stopped running. Your health check endpoint returned 200 — but the application behind it was broken. Silence isn't safety.

✓ No credit card  ·  ✓ 5-minute setup  ·  ✓ Works with any server or monitoring stack

Works with your infrastructure
Linux
AWS
DigitalOcean
Datadog Agent
Prometheus
Any HTTP

Silence looks like health — until it doesn't

The most dangerous server state isn't a red alert — it's no alert at all. When your monitoring stops reporting, everything looks fine. It isn't.

🔕

Monitoring agent crashed silently

Your server monitoring agent crashed due to an OOM error. It stopped sending metrics. Your dashboard showed the last known state — 'healthy.' The server was actually under heavy load and nobody knew.

✅

Health check returned 200, app was broken

Your /health endpoint returned 200 — it always did. It just checked that the server was reachable. Behind it, the database connection pool was exhausted and all requests were failing. The 200 masked everything.

⏰

Heartbeat cron job stopped running

The cron job that sent your monitoring heartbeat stopped running after a system update changed the crontab. No heartbeat for 8 hours. No alert. You assumed everything was fine because nothing was red.

Dead man's switch monitoring for your infrastructure

NotiLens expects a regular signal from your server. If that signal stops arriving — for any reason — NotiLens fires. The absence of a signal is the signal.

🔕

Heartbeat silence detection

Your server sends a regular ping to NotiLens. If the ping stops arriving — for any reason, including a crashed monitoring agent — NotiLens fires. The absence of a signal is the signal.

✅

Deep health check monitoring

Go beyond HTTP 200. Send real application health data — DB connections, queue depth, cache hit rate — and NotiLens monitors it via signal rules and anomaly detection, not just reachability.

🔄

Monitoring-the-monitoring

If your primary monitoring tool goes silent, NotiLens catches it. Use NotiLens as a secondary heartbeat layer — your main monitoring sends a periodic ping, and NotiLens alerts if the pings stop.

Manual rules + auto anomaly detection

You get two layers of detection — not one. Set your own thresholds for what you know matters. NotiLens learns the rest automatically.

⚙️ Manual signal rules
Set exact conditions: thresholds, state changes, custom expressions like amount > $100. Fires only when your rule is met.
🧠 Smart anomaly detection
Auto-learns your baseline per event type. Flags spikes, drops, and unusual patterns without any manual threshold — including things you didn't know to watch for.

What NotiLens sends when servers go quiet

Every alert fires within minutes of silence detection — with the server name, last check-in time, and silence duration so you can act immediately.

NotiLens Live Feed — server-silence
🔕
Server heartbeat stopped — prod-api-02 has not checked in for 8 minutes
Topic: server-silence • Heartbeat gap • 9 min ago
Critical
✅
Health check returning 200 but DB connection count at 0 for last 3 pings
Topic: server-silence • Deep health anomaly • 22 min ago
Warning
🔕
Monitoring agent silent for 2 hours — last ping was from prod-worker-01 at 14:32 UTC
Topic: server-silence • Agent silence • 2 hr ago
Critical
✅
Heartbeat restored — prod-api-02 checking in normally, all metrics healthy
Topic: server-silence • Recovered • 3 hr ago
Resolved
🔕

The most dangerous server state is 'quietly broken.'

No errors, no alerts, just silence — and somewhere behind it, something stopped working. NotiLens is designed specifically to detect this: if the expected signal stops arriving, you're alerted.

⚡ Avg detection time with NotiLens: <60 seconds

Silence monitoring catches what threshold monitoring misses

Threshold-only monitoring only fires when values go wrong. Silence monitoring catches when reporting stops entirely. Here's the gap it closes.

< 60 sec

heartbeat gap detected — even when the process looks healthy

Hours

typical time silent server issues go unnoticed without heartbeat monitoring

5 min

to configure a dead man's switch for your infrastructure

Live in 5 minutes

No agents to install. No infrastructure changes. Add a heartbeat cron job and set your silence threshold — your dead man's switch is live.

1

Create a topic

Create a server-silence topic in NotiLens. This is your dead man's switch.

2

Set up your heartbeat

Configure a regular ping from your server — cron job, monitoring agent, or health check script.

# /etc/cron.d/notilens-heartbeat (every 3 min)
*/3 * * * * root curl -s -X POST \
  https://hook.notilens.com/webhook/TOPIC_ID/send \
  -H "X-NOTILENS-KEY: SECRET" \
  -H "Content-Type: application/json" \
  -d '{"title":"'$HOSTNAME' alive",
     "type":"success"}'
3

Configure silence threshold

Set: "Alert if no heartbeat in 10 minutes." NotiLens fires the moment silence exceeds your window — even if nothing else is red.

Server silence monitoring — common questions

What's the difference between server silence monitoring and uptime monitoring? +
Uptime monitoring checks if your server responds to an external ping. Silence monitoring watches for a signal from inside your server. If your server is up but your application is broken, uptime monitoring says 'healthy.' Silence monitoring catches the gap because your application stops sending its heartbeat.
What if my server legitimately goes quiet during maintenance? +
Configure a maintenance window in NotiLens to suppress alerts during planned downtime. Outside that window, any silence triggers an alert.
Can I send more than just a heartbeat — like actual metrics? +
Yes. Include CPU, memory, disk, DB connection count, or any metric in your heartbeat payload. Configure signal rules in NotiLens to alert when specific values cross thresholds, not just when the ping stops.
Is this a replacement for tools like Datadog or Prometheus? +
No — it's a safety net underneath them. Those tools are great for metrics and dashboards. NotiLens adds a dead man's switch: if those tools stop reporting, or if your server goes silent in a way they don't detect, NotiLens catches it.
How often should I send heartbeats? +
Every 2–5 minutes for production services. Set your silence threshold to 2–3× your heartbeat interval to avoid false alerts from a single missed ping. A 3-minute heartbeat with a 10-minute threshold gives you a 7-minute buffer before alerting.

Start monitoring server silence

The most dangerous server state is quietly broken. Know within minutes when your server stops reporting. Free 7-day trial.

Start Free — 7-Day Trial