How It Works

The technical deep-dive (in plain English).
Learn how OpsPulse eliminates alert fatigue without missing real incidents.

🔍 The Monitoring Flow

1

Health Check

We ping your endpoint every 60 seconds (configurable) from multiple locations. We check HTTP status, response time, and optionally response body.

2

Failure Detection

When a check fails, we don't alert immediately. We mark it as "potentially down" and continue monitoring.

3

Threshold Validation

We require X consecutive failures (default: 3) before declaring an incident. This filters out 1-second blips and network hiccups.

4

Deduplication Check

Before sending an alert, we check: "Did we already alert about this in the last Y minutes?" If yes, we skip it. No spam.

5

Alert Delivery

Only after passing all filters do we send an alert via your configured channels: Telegram, email, or webhook.

6

Recovery Notification

When your endpoint recovers, we send a single "back online" alert. You always know when things are fixed.

🎯 Smart Thresholds

Traditional monitoring alerts on every failed check. OpsPulse uses consecutive failure thresholds to distinguish between real incidents and temporary blips.

Example: 3-Check Threshold

❌ Without Threshold

  • Check 1: FAIL → Alert sent
  • Check 2: Success (1s later)
  • Check 3: FAIL → Alert sent
  • Check 4: Success
  • Check 5: FAIL → Alert sent

Result: 3 alerts for 0 real incidents

✅ With 3-Check Threshold

  • Check 1: FAIL (count: 1)
  • Check 2: Success (count: 0)
  • Check 3: FAIL (count: 1)
  • Check 4: Success (count: 0)
  • Check 5: FAIL (count: 1)

Result: 0 alerts (no 3 consecutive failures)

🔇 Alert Deduplication

When an endpoint is down for an extended period, OpsPulse won't spam you with repeated alerts. We send one alert, then wait for the cooldown period (default: 15 minutes) before sending another.

⏱️

Configurable Cooldown

Set how long to wait between repeated alerts. Default: 15 minutes. Adjust per-endpoint.

📊

Incident Tracking

We continue logging failed checks even during cooldown. You get the full picture without the spam.

🔔

Recovery Alerts

When your endpoint recovers, you always get a notification. No exceptions.

⚙️ Technical Details

🌍

Multi-Region Checks

Monitor from multiple geographic locations to distinguish between local network issues and real outages.

60-Second Intervals

Default check frequency. Configurable down to 30 seconds on paid plans.

📈

Latency Tracking

Track response times over time. Get warnings when latency exceeds your thresholds.

🔐

Auth Support

Monitor endpoints behind basic auth or custom headers. Secure credential storage.

📊

Historical Data

30-day incident history on all plans. Export data via API.

🪝

Webhooks

Integrate with Slack, Discord, PagerDuty, or custom systems via webhook alerts.

📝 Configuration Example

Simple JSON config. No UI required. Version control your monitoring setup.

{ "endpoints": [ { "name": "API Production", "url": "https://api.example.com/health", "method": "GET", "timeout": 10, "threshold": 3, "cooldown": 900, "alerts": ["telegram", "email"] }, { "name": "Website", "url": "https://example.com", "method": "GET", "expected_status": 200, "threshold": 2, "cooldown": 600, "alerts": ["telegram"] } ], "alert_channels": { "telegram": { "bot_token": "your-bot-token", "chat_id": "your-chat-id" }, "email": { "to": "[email protected]" } } }

Ready to Eliminate Alert Spam?

Start monitoring in 5 minutes. Free tier includes 3 endpoints.