Docs / Get started
What CountWatch does
What a watch is, what counts as usual, and the three kinds of alert.
A watch follows one number
A watch follows one count over time: orders, sign-ups, payments, finished jobs. Add a tag such as shop:EU and each value gets its own watch. CountWatch keeps 90 days of counts.
It learns what is usual
Each watch learns what is normal for it, hour by hour through the week, so a Monday morning is judged against Monday mornings, not a Saturday night. While a new watch gets to know its pattern, simple starter rules alert. Bring in past data and alerts start today.
Three kinds of alert
| Alert | What happened |
|---|---|
Spike (API spike; your own number: max) | The number rose far above usual, or above your own number. |
Drop (drop; your own number: min) | The number fell far below usual, or below your own number. |
Silence (no_data) | A sender stopped. For a Webhook URL, set how long a gap is too long on the watch's Rules tab; otherwise it shows as Stopped. |
How often it checks
Both plans check every 5 minutes.
Where alerts go
Slack, a webhook your agent reads, e-mail, or PagerDuty on Pro. Each alert says what happened in plain words, for example:
orders rose to 1,245 in the last hour. Usually about 300 on a Wednesday afternoon.
You stay in charge
Set your own limit for a watch. Tell CountWatch about a planned sale or deploy (under Known events on the watch's page, or ask your agent), and alerts hold while it runs. If an alert was wrong, press False alarm, and CountWatch learns from it for that watch. See When an alert fires and Planned changes and feedback.
For agents: this page as Markdown.