Why a “monitoring stopped” alert is a feature, not noise
The most dangerous state for a risk monitor is silent failure. Chartping fires a fail-loud “monitoring stopped” alert when it loses sight of your account — here’s why.
The worst failure mode for any risk monitor is the quiet one: it stops watching and says nothing, so you assume everything is fine. Chartping is built the opposite way — when it loses sight of your account, it fires a fail-loud “monitoring stopped” alert. Silence is never treated as safety.
The silent-failure trap
A terminal crashes. A VPS reboots for an update. Wi-Fi drops. With most tools you’d never know — the dashboard just stops updating, and you find out when it’s too late. For a tool whose entire job is to warn you, going quiet at the wrong moment is the one failure that matters most.
Loud by design
So Chartping inverts it. Losing visibility is itself a risk event: if the connection drops or the terminal closes, you get a critical alert saying so. When coverage returns, a “monitoring resumed” notice confirms it. So you’re not left assuming silence means safety — you can see whether you’re actually being watched.
It escalates until you acknowledge
Like any critical breach, a “monitoring stopped” alert re-notifies until you acknowledge it — one tap marks it handled. A missed notification is treated as still-unhandled, never as done. That’s the same principle behind how the alerts work generally: best-effort delivery — whether it reaches you by push, SMS or a signed webhook — but honest about its own gaps.
It’s a small feature that changes how much you can trust the quiet. More on the model on the security page and in everything Chartping watches — and it’s especially useful when your terminal lives on a VPS you aren’t looking at.
Frequently asked
What triggers a “monitoring stopped” alert?
Losing sight of an account — the MetaTrader terminal or agent closing, a machine sleeping, or a connection dropping. Chartping treats that as a risk event and tells you, rather than going quiet.
Won’t that spam me?
It’s a critical, infrequent event, not routine chatter. It fires when coverage actually stops, and a “monitoring resumed” notice confirms when you’re covered again.
When does monitoring resume?
As soon as the connection is back and Chartping can read your account again — you get a “monitoring resumed” confirmation so you know the gap has closed.