The mistake is treating every account the same. A prop firm evaluation, a live investor account and a forward test account have different rules and different alert needs. Multi-account monitoring works when each account has a purpose, a risk model and a heartbeat.
Group accounts by job
Create groups for prop firm accounts, live accounts, forward tests and strategy research. Then review each group with the right lens. Prop accounts need drawdown-room monitoring. Live accounts need exposure and margin visibility. Forward tests need EA version and magic-number context.
Build a dashboard around exceptions
A multi-account dashboard should make problems obvious: stale terminal, drawdown close to limit, margin level falling, unusually large floating loss or missing telemetry. The healthy accounts should be scan-friendly, not noisy.
Alert by account type
| Account type | Primary alerts |
|---|---|
| Prop firm | Daily drawdown, max drawdown, reset time. |
| Live account | Margin level, open exposure, stale terminal. |
| Forward test | EA version, equity curve, magic number behavior. |
Where xTriel fits
xTriel was built for this exact operating problem: read-only MT5 telemetry, live dashboard state, drawdown monitoring and alerts across accounts. For the single-account foundation, read How to monitor MT5 accounts.
Give every account a stable identity
A multi-account screen should never rely on a broker nickname alone. Store the MT5 login, server, account currency, leverage, environment and an operator-friendly label. The login and server combination distinguishes accounts that otherwise look identical. Keep demo and live accounts visually and operationally separate so a test account cannot be mistaken for production exposure.
Normalize presentation without erasing differences. Display money values in the account’s own currency and use percentages for comparisons across account sizes. A $500 loss is minor on one account and terminal on another; drawdown percentage, margin level and remaining rule room make the distinction visible.
Build account and portfolio views
The account view answers “what is happening here?” The portfolio view answers “where is shared risk accumulating?” Group by strategy, broker, VPS and prop-firm rule set. If three accounts run the same EA on the same symbol, they are correlated even if each account is inside its individual limit.
For example, four $50,000 accounts each show only 0.6% open loss. Viewed independently, none looks urgent. If all four run the same EURUSD strategy from one VPS, the operator has $200,000 of correlated exposure and a single operational failure domain. The portfolio view should surface that concentration and the shared host.
Route alerts by severity and ownership
- Warn when one account approaches its declared drawdown or margin threshold.
- Escalate when multiple accounts become stale on the same host; this points to a VPS or network problem.
- Include account label, login suffix, server, observed value, threshold and timestamp in every message.
- Deduplicate repeated alerts, but send a recovery event when telemetry returns.
Test the system by deliberately stopping one terminal, then the whole VPS, and confirming the alerts distinguish those cases. Continue with the VPS measurement guide and the alert design guide. Multi-account monitoring is most useful when it points to the common cause, not merely a longer list of red rows.
Roll out without losing account coverage
Build an inventory before onboarding: expected login/server pairs, owner, VPS, strategy, currency and reporting interval. Reconcile that inventory against accounts seen by the monitor. An account that never connected must remain visible as missing; otherwise the dashboard can look healthy while omitting the account that needs attention.
For day-to-day review, sort first by stale state and smallest remaining risk room, then by ordinary P/L. Add a coverage check that reports expected accounts, reporting accounts and unknown accounts. Review changes to the inventory like code: removing an account should require an explicit reason, while discovering an unknown login should create an investigation rather than silently adding it to production reporting.
Primary source
Technical reference: official MetaTrader documentation. Broker and prop-firm terms can differ; verify the rules for the exact account you operate.
Connect each terminal with the read-only Reporter EA and monitor accounts by group.