Your API Error Rate is Climbing.
Are You the Last to Know?
It started at 0.5% errors. Two hours later it was 12%. By then, users were hitting failures, retrying, and dropping off. Your on-call found out from a tweet.
✓ No credit card · ✓ 5-minute setup · ✓ Works with any API stack
API degradation is gradual — and invisible until it's critical
Error rates climb slowly. Latency spikes quietly. Endpoints go silent after deploys. By the time your monitoring alerts, users have already felt the pain.
Error rate crept up while everyone slept
Your API error rate climbed from 0.5% to 8% over 90 minutes. No threshold was crossed in your existing monitoring because it only alerted on complete outages. Users were getting 500s the entire time.
Latency spike killed conversion silently
Your checkout API started responding in 4 seconds instead of 200ms. No errors — just slow. Users abandoned carts. You found out when conversion dropped in the weekly report.
Endpoint went silent — no requests, no errors
After a deploy, traffic to your payments endpoint dropped to zero. No 500s, no errors — just silence. A misconfigured route meant users were hitting a 404 that your monitoring ignored.
Error rate intelligence that fires before users notice
NotiLens watches error rates, latency, and traffic volume across your API endpoints — and alerts the moment degradation begins, not when it peaks.
Baseline error rate monitoring
NotiLens detects API error rate degradation via your signal rules and auto-learned anomaly detection — catches gradual climbs and sudden spikes, even without a manually configured threshold.
Latency anomaly detection
NotiLens detects latency degradation via your signal rules and auto-learned anomaly detection — fires when response times deviate from normal, even if the error rate still looks healthy.
Traffic silence detection
Monitor expected request volume. If an endpoint goes unusually quiet — after a deploy, a routing change, or a client-side bug — NotiLens alerts before you lose the data trail.
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.
amount > $100. Fires only when your rule is met.What NotiLens sends when your API degrades
Every alert fires within 60 seconds of detection — with the specific endpoint, metric, and threshold so you can diagnose immediately.
A quiet endpoint isn't healthy — it might be broken.
Zero traffic after a deploy means your routing change sent requests nowhere. NotiLens detects the silence before you lose an hour of production data.
Catch degradation early — before it becomes an outage
A latency spike that hits users for 2 hours costs far more than a year of NotiLens. Here's what teams typically recover.
error rate degradation detected — not just complete outages
typical detection lag when monitoring only fires on full downtime
to start monitoring error rates, latency trends, and endpoint silence
Live in 5 minutes
No infrastructure overhaul. Instrument your middleware or forward from your API gateway. Set your first threshold and NotiLens starts watching.
Create a topic
Create an api-errors topic in NotiLens. One topic can aggregate multiple endpoints or create one per endpoint for granular monitoring.
Forward error events
Send error rate data from your API gateway, middleware, or error tracking tool to NotiLens.
https://hook.notilens.com/webhook/TOPIC_ID/send \
-H "X-NOTILENS-KEY: SECRET" \
-H "Content-Type: application/json" \
-d '{"title":"Error rate spike",
"message":"12% errors — baseline 0.5%",
"type":"urgent"}'
Set your thresholds
Configure: "Alert when error rate exceeds 3% over 5 minutes." Done.
More ways to monitor your stack
API error rate monitoring — common questions
Start monitoring your API health
Know when error rates climb, latency degrades, or endpoints go silent — before users notice. Free 7-day trial.
Start Free — 7-Day Trial