Team
People you add here sign in with their own login and see the same sites and reports as you.
Notification channels
Where StoreWatcher sends your alerts. View sent alerts
No channels yet.
AI drafts (BYOK)
Optional. RCA and status-page drafts stay unpublished until a human confirms. Incident titles are treated as untrusted. The compiler cannot ack, resolve, or disable monitors.
No key configured — drafts use a structured template.
Anomaly Detection Thresholds
Configure when the system should alert you about unusual behavior in your e-commerce platforms. These thresholds are applied on top of each store’s statistical baseline.
Alert when uptime drops by this percentage from the baseline
Alert when security risk score increases by this percentage from the baseline
Alert when this many monitors are down simultaneously
Degraded Performance Thresholds
When your store's own self-check is slower than these limits, StoreWatcher opens an early “slowing down” advisory — before the store is slow enough to be marked down. Tune these to your store's normal baseline: a store that's usually 20ms and a store that's usually 800ms want very different warning lines.
Warn when a self-check DB query is slower than this. Default 2000ms. Must be under the hard-down limit of 8000ms.
Warn when representative render work is slower than this. Default 4000ms. Must be under the hard-down limit of 15000ms.
Warn when server CPU usage climbs above this. Default 85%. Only fires on hosts that expose CPU stats; ignored where they aren't readable.
Warn when server RAM usage climbs above this. Default 85%. Only fires on hosts that expose memory stats; ignored where they aren't readable.
Maintenance Windows
During a maintenance window, checks still run and are recorded, but StoreWatcher won't open new incidents or send alerts — so planned work doesn't page you. Scope a window to one monitor, or leave it org-wide to cover everything.