WATCHLOG PRODUCT · OPERATIONS

Alert on anything. Notify the right team.

Multi-condition alert rules, anomaly detection, escalation policies, and delivery to Slack, Telegram, PagerDuty, email, or any webhook — from one rule engine.

Operations
AND/OR conditions·Anomaly detection·Any delivery channel

THE PROBLEM

Too many false positives. Too many blind spots.

Simple threshold alerts fire constantly on normal fluctuations. Meanwhile, subtle degradations that matter go undetected because nobody thought to create the right rule. The result: alert fatigue on one end, silent failures on the other.

Single-threshold alerts cause alert fatigue

CPU > 80% fires 40 times a day. Engineers stop looking. Then it fires when it actually matters — and nobody notices.

Routing is an afterthought

All alerts go to #alerts channel. Everyone ignores it. Nobody owns it. Nothing gets fixed.

Anomalies are invisible

Error rate is 0.3% instead of the usual 0.05%. It has never crossed your 1% threshold. Nobody knows.

WHAT'S MONITORED

Everything Alerts & Webhooks captures.

Real signals collected by the Watchlog Agent — available in your dashboard within 60 seconds of enabling.

Multi-condition rules

Combine up to 5 conditions with AND/OR logic — CPU > 90% AND memory > 85% AND duration > 5min.

Anomaly detection

Machine learning baseline detects deviations from normal without manual threshold configuration.

Alert deduplication

Identical alerts deduplicated within a configurable time window — one Slack message, not 50.

Escalation policies

Alert primary team first, then escalate to secondary on-call after N minutes without acknowledgment.

Multi-channel delivery

Slack, Telegram, PagerDuty, OpsGenie, email, and arbitrary webhook targets per alert rule.

Log-based alerts

Alert on log pattern frequency — "ERROR count > 20/min for checkout-service for 3 consecutive minutes."

LIVE VIEW

Alert rules — active and routing.

See all your alert rules, their current status, last fired time, and configured destinations.

Alerts & Webhooks  ·  Live
Rule NameConditionStatusLast FiredDestination
High CPU — prod-api-3CPU > 90% (5 min) FIRING2 min agoSlack #on-call
Checkout error spikeERROR logs > 15/min FIRING4 min agoPagerDuty
DB connection warningconnections > 180/200 OK12h agoSlack #infra
API uptime/api/health fails 2 regions OK2d agoEmail + Telegram
Memory anomalyAnomaly detected OK5d agoWebhook

CAPABILITIES

What Alerts & Webhooks gives you.

Composite conditions

Combine multiple signals in one rule — avoid noisy alerts by requiring corroboration.

Auto-baseline anomaly detection

Watchlog learns normal metric behavior and alerts on deviations — no manual threshold needed.

Alert history and timeline

Full history of every alert — when it fired, how long it lasted, and who acknowledged it.

Escalation and on-call rotation

Define primary and secondary on-call teams. Escalate automatically after an unacknowledged window.

Webhook payload customization

Send structured JSON to any endpoint — Zapier, JIRA, custom incident systems, or internal handlers.

Alert grouping

Group related alerts into a single incident notification to reduce noise during cascading failures.

USE CASES

How engineering teams use Alerts & Webhooks.

Composite resource alert

CPU > 85% AND memory > 80% AND sustained > 10min → PagerDuty. Single metrics alone are fine. Together they signal real saturation.

CPUMemoryComposite

Anomaly-driven on-call

Error rate at 0.3% — 6× its usual baseline. Anomaly detection fires PagerDuty. Threshold alert at 1% never would have caught it.

AnomalyError RateProactive

Log pattern alerting

Alert fires when "payment failed" appears more than 10 times per minute in checkout-service logs. Routes to Slack #payments.

LogsPatternsRouting

Webhook-driven automation

Alert fires → webhook POST to internal handler → auto-scales the affected service. Alerts as automation triggers.

WebhooksAutomationAuto-scaling

PLATFORM FIT

Alerts & Webhooks inside the Watchlog platform.

Alerts connects every Watchlog signal — metrics, logs, uptime, traces, and anomalies — to the right team via any channel. It is the operational layer that makes all other products actionable.

All MetricsAlert on any collected signal
Log MonitoringLog pattern and count alerts
AI AnalysisAI-detected anomaly alerting

QUICK START

Start Alerts & Webhooks in under 2 minutes.

No YAML. No complex configuration. The Watchlog Agent handles discovery automatically.

01

Install the Agent

One curl command on your host. The Watchlog Agent starts immediately.

sudo apiKey="$WATCHLOG_API_KEY" server="$WATCHLOG_SERVER" MEMORY="300M" bash -c "$(curl -L https://watchlog.io/ubuntu/watchlog-script.sh)
02

Enable Alerts & Webhooks

Go to Watchlog → Alerts → New Rule. Select metric, log, or uptime condition. Choose your delivery channel. Done.

03

Data appears in 60s

Your first alert rule activates immediately. Test it by triggering the condition or using the built-in test button.

GET STARTED

Start monitoring with Alerts & Webhooks.

Multi-condition rules, anomaly detection, and any-channel delivery — one alert engine for your entire stack.

Questions? Talk to us → [email protected]