Multi-instance monitoring means reviewing more than one Gunbot setup from a single interface. It is useful when you run separate servers, exchange accounts, strategies, or trading environments and need a quick way to see which setups are active, stale, disconnected, or requiring attention.
What This Feature Does
When you run more than one Gunbot setup, for example bots split by exchange, the workspace gives you a single place to move between them. You can check which connection you are looking at, whether it is active, what it is trading, and what needs attention without treating every server as a separate island.
Example Workflow
When you run multiple setups, open the workspace, select a connection, review status and pair activity, then switch to another connection without opening a separate browser dashboard for every bot.
Common Mistakes
Do not assume every instance has the same exchange permissions or trading mode. A setup can be connected but still be read-only, in demo mode, missing permissions, or running strategy settings that need review before you rely on them.
Trading Reality
It gives Gunbot a browser workspace for monitoring, strategy work, backtesting, risk review, history, and exchange-connected operations. These pages explain what the product does. Your account data stays on your local trading bot, behind login.
Operational Limits
The dashboard depends on the connected Gunbot instance, the exchange API, and the network between them. It can make problems easier to notice, but it does not remove market risk or take responsibility away from you: exchange permissions, strategy settings, open orders, and capital allocation still need your review.
Plain Definition
Multi-instance monitoring means operating more than one automated trading environment without treating each one as a disconnected island. You may separate accounts by exchange, strategy family, risk profile, market type, region, or research versus production. The monitoring layer should make those boundaries visible.
What To Check Across Instances
Before changing anything, make sure the selected instance is the one you intend to work on. Check whether it is live, demo, local, remote, cloud-hosted, or private, whether balances and orders are fresh, whether API permissions differ from your other setups, and whether risk is concentrated across several bots even when each bot looks small on its own.
Failure Modes
The common failure mode is not dramatic: you edit the wrong instance, trust stale dashboard data, assume one exchange account has the same permissions as another, or miss overlapping exposure across bots that trade correlated assets.
External references
- official Gunbot Monitor overview: Official background on monitoring several bots and pairs from one dashboard.
FAQ
Does multi-instance monitoring trade on its own?
No. It is a working view. Trading behavior comes from the connected Gunbot setup and your configuration.
Can I use it for separate exchanges?
Yes, as long as your Gunbot setup and permissions cover those exchanges.
Why would you run multiple instances?
Common reasons include separating exchanges, testing strategies independently, isolating risk, running spot and futures separately, or keeping one private setup behind a VPN while using another through hosted access.
What is the biggest execution risk?
Changing or trusting the wrong instance. The selected connection, market type, exchange, and live/demo state should be checked before any action.
Last updated: