Noetrix Sentinel
- Utilities
- Version: 1.10
Noetrix Sentinel 1.10
Noetrix Sentinel is a native, read-only MetaTrader 5 operational supervision utility. It monitors terminal connectivity, latency, trading permissions, chart and EA presence, watched market feeds, optional Magic mappings, alerts and diagnostic evidence from a single chart.
## Safety and distribution
- MetaEditor result: `0 errors, 0 warnings`.
- Entry point: `MQL5/Experts/NoetrixSentinel/NoetrixSentinel.mq5`.
- No trading library, order submission, position close, order deletion, restart or account mutation.
- No DLL, WinAPI, WebRequest, cloud, telemetry, Python or external executable.
- Configuration, acknowledgement state and events are stored locally per account.
- Market distribution needs only the compiled `NoetrixSentinel.ex5`; the fonts are embedded resources.
- Algo Trading is not required for monitoring.
## Operational pages
- **Overview**: connection, feed state, permissions, health, EA summary, spreads, resources, active alerts and recent events.
- **Terminal**: professional cards for connection, latency, terminal facts, resources, permissions, account state and the complete health-score calculation.
- **Expert Advisors**: paginated chart discovery and configurable Magic monitoring.
- **Data Feeds**: paginated bid/ask, spread, average, maximum, samples, last tick, tick age, market state and status.
- **Alerts**: deduplicated `ACTIVE`, `ACKNOWLEDGED` and `RESOLVED` lifecycle with first/last seen and occurrence count.
- **Event Log**: persistent Sentinel events with export and clear-display actions.
- **Settings**: monitoring thresholds, manual watchlist, Magic mapping editor, privacy architecture and diagnostics.
## Persistent configuration
Sentinel creates `MQL5/Files/NoetrixSentinel_Config_<login>.ini`. The following values survive terminal restarts:
- manual watchlist symbols;
- Magic mappings;
- ping warning and critical thresholds;
- stale-tick threshold;
- spread warning and critical multipliers;
- minimum spread samples;
- margin warning and critical thresholds;
- alert cooldown;
- fast and slow refresh intervals;
- Magic inactivity and heartbeat thresholds;
- active alert acknowledgement keys.
Missing or invalid configuration files are handled by validated defaults. No password or credential is stored.
## Watchlist and feeds
The effective watchlist combines three sources:
- open charts (`AUTO`);
- open positions (`AUTO`);
- comma-separated manual symbols (`MANUAL`).
Feed states are `NORMAL`, `ELEVATED`, `HIGH SPREAD`, `STALE`, `NO DATA` and `MARKET CLOSED`. Broker trading-session metadata is used when available, and a closed market is never treated as a failure. Spread averages and maximums are observations since Sentinel start or the last statistics reset; they are not presented as broker history.
## Magic mapping and cooperative heartbeat
Mappings are stored as:
```text
Trend Engine=10001|EURUSD|TrendEA|180|0
Mean Reversion=10002||MeanEA|1440|1
```
Fields are alias, Magic, optional symbol, optional EA name, inactivity threshold in minutes and whether a cooperative heartbeat is expected.
Statuses are `ACTIVE`, `IDLE`, `NOT FOUND` and `HEARTBEAT STALE`. Sentinel never labels an EA as dead because it has not traded. A compatible EA can publish `NOETRIX_HEARTBEAT_<MAGIC>` as a terminal Global Variable whose value is its last heartbeat datetime. Non-cooperative EAs correctly display heartbeat `N/A`.
## Explainable health score
| Category | Weight | Evidence |
|---|---:|---|
| Connection | 30 | Native broker connection |
| Data Feed | 20 | Watched feeds; market-closed is neutral |
| Trading Permissions | 15 | Terminal, account and expert permissions |
| EA Monitoring | 15 | Optional configured expectations |
| Latency | 10 | Configurable warning and critical levels |
| Resources | 10 | Native disk and memory evidence |
An optional category that is not configured is removed from the available weight. The Terminal page displays available weight, raw score and the normalized result, so no score is opaque.
## Alert lifecycle
Sentinel supports broker disconnect/reconnect, high ping/recovery, stale feed/recovery, high spread/normalization, missing expected EA, stale Magic activity, stale cooperative heartbeat, disabled trading permissions, low free disk, honest terminal memory pressure and low margin level.
Repeated conditions update one alert record. The occurrence count advances only after the configured cooldown. Recovery resolves the record and adds a clear recovery event. Acknowledgement state for active alerts is persisted locally.
## Performance model
- Fast loop: connection, ping, ticks, positions and alert state.
- Slow loop: charts, EA discovery, resources, disk and complete Magic refresh.
- Native `OnTradeTransaction` invalidates cached trading activity immediately.
- Historical Magic scans are cached instead of running every second.
## Honest limitations
- Third-party EA internals are unknowable without explicit cooperation.
- Broker session metadata can be incomplete; Sentinel shows `UNKNOWN` rather than inventing state.
- No instantaneous CPU percentage is fabricated; native CPU-core count is shown.
- The event log is Sentinel's own operational journal, not the complete global MetaTrader journal.
