A small but useful detail from the settings — telemetry is now a toggle. ⚙️
If you opened any EASY bot's inputs panel after the update, you may have noticed a new "=== LOGGING ===" section. Here's what's in there and why it matters.
Trade results in log — keeps trade outcomes in the MT5 log
Export trade results to CSV — optional CSV export for your own records
Log trade events — full event-level logging
Log trading errors — errors only
Send logs to Control Center — the toggle that controls telemetry to our side
Log send interval — how often the bot reports (in minutes, min 1)
Telemetry detail level — Off / EventsOnly / Full
The two that actually change behavior are "Send logs to Control Center" and "Telemetry detail level." Together they decide how much the bot talks to our infrastructure.
If you turn telemetry off entirely, here's what happens:
— Slightly faster bot reaction, because no CPU is spent on telemetry packaging
— Higher cycle frequency on busy symbols, especially noticeable on Scalperology on ECN accounts
— Lower CPU and lower outbound network traffic
— No more "idle" detection, no AI-assisted support analytics in the portal, and the "How my bots read the market" widget goes quiet
What you give up is exactly what you save. With telemetry off, the bot is leaner, but if you open a support ticket I can no longer pull the rejected-signal history, broker-execution context, or the parameter trail that lets me diagnose your specific setup in minutes. I'm essentially blind to your bot's behavior — I can only help based on what you describe.
My honest recommendation:
— Telemetry ON if you want the support portal's AI assist, faster ticket resolution, and the live "how the bot reads your market" view in your dashboard
— Telemetry OFF if you're running on a low-spec VPS, metered connection, or simply prefer to operate fully offline — and you're comfortable diagnosing issues yourself
In v10.15 we already cut the default telemetry footprint by 5–10x (event-driven, no more counting filter rejections on every tick), so for most users keeping it on costs essentially nothing. But the toggle is there if you want it, and that's the point — your bot, your call.
In future posts I'll walk through the rest of the input panel — Authorization Server, terminal screenshots, scheduled hours, news protection, and how each parameter actually shifts bot behavior.
Questions about a specific setting → @forexroboteasybot
Test first. Decide with data.
#EasyBots #MT5 #Telemetry #BotSettings #FxRobotEasy
If you opened any EASY bot's inputs panel after the update, you may have noticed a new "=== LOGGING ===" section. Here's what's in there and why it matters.
Trade results in log — keeps trade outcomes in the MT5 log
Export trade results to CSV — optional CSV export for your own records
Log trade events — full event-level logging
Log trading errors — errors only
Send logs to Control Center — the toggle that controls telemetry to our side
Log send interval — how often the bot reports (in minutes, min 1)
Telemetry detail level — Off / EventsOnly / Full
The two that actually change behavior are "Send logs to Control Center" and "Telemetry detail level." Together they decide how much the bot talks to our infrastructure.
If you turn telemetry off entirely, here's what happens:
— Slightly faster bot reaction, because no CPU is spent on telemetry packaging
— Higher cycle frequency on busy symbols, especially noticeable on Scalperology on ECN accounts
— Lower CPU and lower outbound network traffic
— No more "idle" detection, no AI-assisted support analytics in the portal, and the "How my bots read the market" widget goes quiet
What you give up is exactly what you save. With telemetry off, the bot is leaner, but if you open a support ticket I can no longer pull the rejected-signal history, broker-execution context, or the parameter trail that lets me diagnose your specific setup in minutes. I'm essentially blind to your bot's behavior — I can only help based on what you describe.
My honest recommendation:
— Telemetry ON if you want the support portal's AI assist, faster ticket resolution, and the live "how the bot reads your market" view in your dashboard
— Telemetry OFF if you're running on a low-spec VPS, metered connection, or simply prefer to operate fully offline — and you're comfortable diagnosing issues yourself
In v10.15 we already cut the default telemetry footprint by 5–10x (event-driven, no more counting filter rejections on every tick), so for most users keeping it on costs essentially nothing. But the toggle is there if you want it, and that's the point — your bot, your call.
In future posts I'll walk through the rest of the input panel — Authorization Server, terminal screenshots, scheduled hours, news protection, and how each parameter actually shifts bot behavior.
Questions about a specific setting → @forexroboteasybot
Test first. Decide with data.
#EasyBots #MT5 #Telemetry #BotSettings #FxRobotEasy
🙏11👍7