Blog · Monitoring
A multi-account MT5 dashboard that tells you where to look
Four ways to monitor multiple MT5 accounts compared, the nine columns an operational dashboard needs, and the design rules that make it trustworthy at a glance.
Once you run more than three MT5 accounts, checking terminals one by one stops being supervision and becomes a ritual. A multi-account dashboard should replace it, but most attempts fail for the same reason: they show plenty of numbers and none of them tells you where to look first. This guide covers the options available, the columns that matter, and the design rules that make a dashboard something you can trust at a glance.
Four ways to see several accounts at once
| Approach | Good for | Limits |
|---|---|---|
| Several terminals on one VPS + RDP | Two or three accounts, full control | No aggregation, no alerts, you are the monitor. RAM grows with every instance. |
| MetaTrader mobile app | Checking one account on the go | One account at a time; shows balance and positions, not whether the EA is alive. |
| Statistics sites (Myfxbook, FXBlue and similar) | Performance analytics, sharing a track record | Need the investor password; update in minutes to hours; they measure results, not operational state. |
| Telemetry pushed by the EA to a monitor | Fleets, prop accounts, anything where "is it running and within rules?" matters | Requires adding an include to the EA or running a reporter EA on each account. |
These are complementary. Analytics sites answer "is this strategy good?". An operational dashboard answers "is everything I run doing what it should, right now?". This article is about the second question.
The columns that earn their place
- Account as
server::login, plus a human label. Broker names alone collide as soon as you have two accounts with the same firm. - Freshness: age of the last report, with a state (fresh, stale). It is the first column because every other number is meaningless if it is old.
- Trading allowed: whether the terminal, the EA and the account all permit trading. One red cell here explains a quiet day.
- Daily loss used: percentage of the daily allowance consumed, not raw equity.
- Drawdown from peak on equity.
- Open exposure: total lots per symbol, and number of positions.
- Lot audit: last executed lot against the expected lot, flagged beyond tolerance.
- EA name, magic and version. After an update you need to see which accounts still run the old build.
- Last decision and block reason: "blocked: spread" for six hours is information you want without opening the terminal.
Leave out total profit, win rate and the equity chart. They are analytics; they invite you to stare at the dashboard and they push the operational columns off the screen.
Design rules
Sort by what needs attention
Default order should be worst first: stale accounts, then the highest share of daily loss used, then lot-audit flags. Alphabetical order hides the one row that matters among twenty that do not.
Let state drive colour, not values
Three states are enough: fine, needs a look, act now. Tie them to written thresholds (for example 50% and 80% of the daily allowance, five minutes of silence). A dashboard where colour follows someone's taste trains people to ignore colour.
Show age next to every number
A value without its timestamp is a rumour. When an account goes stale, grey out its derived metrics and say "unknown" rather than leaving the last good figure on screen.
Keep it read-only
It is tempting to add a "close all" button. Every control that can act on an account is also something that can be clicked by mistake, abused with a stolen session, or triggered by a bug. A monitor that cannot trade cannot make a bad day worse, and it is far easier to grant access to: a risk manager, a client or a prop firm reviewer can see everything without being able to touch anything.
Separate tenants properly
Personal accounts, client accounts and test accounts belong in separate scopes with separate credentials, not in one table with a filter. Mixing them produces alerts nobody owns and, sooner or later, a screenshot shared with the wrong person.
A practical start
- List every account you run, with the rule set that applies to it (own risk limits or the prop firm's).
- Put a reporter on each one, sending on a timer every 30–60 seconds.
- Configure only two alerts at first: stale for more than five minutes, and 70% of daily loss used.
- Live with it for two weeks, then add lot-audit and per-EA drawdown once the noise level is known.
- Export a weekly CSV of the key series. The live view is for today; the series is what you show an auditor.
Frequently asked questions
Can I monitor multiple MT5 accounts from one screen?
Yes. Either run several terminals side by side, use a statistics site with investor passwords, or have each EA push telemetry to a monitoring dashboard that aggregates all accounts.
How is this different from Myfxbook or FXBlue?
Those services analyse performance over time. An operational dashboard shows current state: whether each EA is alive, allowed to trade, within its daily loss allowance and sizing lots as expected.
Does a monitoring dashboard need my investor password?
Not when the EA pushes telemetry itself. The terminal sends data out; nothing logs into your account.
Which column matters most?
Freshness. Every other number is meaningless if the data behind it is old, so data age should be visible on every row.