Back

What Warning Does

A quick overview of what Warning watches for and what you’ll see when something goes wrong.
Warning blog placeholder image

Warning is a lightweight monitoring layer for your API. It helps you notice problems early — before customers report them — and it keeps the output simple enough to act on.

What it watches for

  • Error spikes: when a much larger share of requests starts failing.
  • Error floods: when the number of failed requests suddenly jumps.
  • Traffic anomalies: when request volume is unusually high or low for that time of day.
  • API key sharing: when the same key is used from many different IPs (often a sign of a leaked key).

What you get

  • Dashboard with recent activity and open incidents.
  • Alerts that include the time window, severity, and quick context (what changed vs normal).
  • Details on click: drill into the paths or IPs involved without cluttering the main view.

Why this approach works

Most alerting systems fail because they are too noisy or too complicated to trust. Warning focuses on a small set of signals that are easy to understand. The goal is to help you make one decision quickly: do I need to act right now?

FAQ

Do I need to set up a big monitoring stack first?
No. The idea is to start with simple signals that catch common incidents, then expand only when you have a real need.
What is API key sharing?
It’s when the same API key shows up from many different IP addresses. That can mean a key was leaked, copied into a public client, or shared across multiple apps.

Related

Why a Dedicated Alerting App Is Better Than a “Platform”