Notify Health watches Windows PCs, VPS instances, trade terminals, and connected platform workflows for heartbeat loss, offline periods, and recovery. Instead of discovering downtime after the fact, you see when a machine or terminal stops reporting.
Health inside Notify covers machine heartbeat and terminal heartbeat. Trade Monitoring covers positions and orders. Keeping those signals separate is the architectural difference: an offline alert should mean health, not a mixed trade message.
Watches a Windows PC, VPS, or server as a machine. The question here is operational: is the machine alive and still reporting?
Watches the trading runtime as a platform-health layer, not as a trade feed. The question here is whether MT4, MT5, or another connected trading-platform workflow is still active and reporting.
The failure is often not dramatic. A machine stops reporting. A terminal disconnects. Nobody notices. Health monitoring matters because reaction time usually matters more than post-fact explanation.
A VPS or Windows machine can go quiet while everything still appears normal from a distance. Manual checking usually happens too late.
A platform session can drop without a human seeing it in real time. Health alerts shorten that blind period.
Refreshing remote desktops, terminals, and logs just to prove things are alive does not scale well and weakens oversight.
A terminal going offline and a position closing are different operational facts. Notify keeps those signals separate, so the alert feed stays easier to trust.
This module is valuable because it turns reporting continuity into a usable operational signal. It tells you whether the environment is still alive, when it stopped, and when it came back.
Health is driven by regular reporting, not guesswork. Offline thresholds are configurable per source; Trade Terminal health commonly uses a 120-second missed-heartbeat threshold.
When reporting stops long enough, Notify Health escalates that gap into an actionable offline event.
You do not just see that something broke. You also see when heartbeat returns and recovery is confirmed.
Health tells you operational status. Trade Monitoring tells you about positions and orders. The split keeps both feeds cleaner.
Health events can surface on dashboard, mobile push, or Telegram so awareness reaches the real operator path.
Follow more than one machine or terminal from one monitoring layer instead of proving health manually source by source.
Windows Monitor or Terminal Health sends heartbeat data on an expected rhythm.
If that rhythm breaks long enough, the module treats it as a health problem instead of waiting for manual discovery.
Offline and recovered events become explicit operational states that can be viewed, routed, and reviewed.
Alert routing sends awareness where it is most likely to produce fast reaction.
Choose Notify Windows if you only need Windows machine and VPS health monitoring. Choose Notify Pro when you also need terminal health, trade monitoring, profit rules, and price watch in the same operational dashboard.
