Health Watchdog and alerts
Designed to keep checking after setup day and tell you when events stop arriving.
updated
Coming to PixelCapi Pro Outline — facts still to be confirmedNot shipped yet. Health Watchdog is in development. This page describes what it is designed to do, in future tense, and will be rewritten as reference documentation when it ships. Release notes go out on the changelog.
This article is a structured outline. Its headings and scope are settled; the
specific values, screens and steps are marked TODO(owner: verify)
until they have been checked against the plugin itself. Blueprint §7 is explicit
that no article may state plugin behaviour that has not been verified.
What it is designed to do
Learn what normal looks like for your store, treat silence as a signal, and raise an alert when an event type that should be firing has not fired — rather than waiting for you to open a dashboard.
What already helps today
The two most common causes of silent breakage are designed out rather than monitored: the cache-proof architecture, and verification that is allowed to report failure. See LiteSpeed and REST caching and Token error #100.
Outline still to fill
TODO(owner: verify) — alert channels, thresholds, how a baseline is established, and what happens on a store with genuinely seasonal traffic. None of this can be documented before it ships, and guessing at thresholds would be worse than leaving it blank.
Was this page helpful?