Monitoring Your Bot
Every VolatiCloud bot streams trade events, PnL changes, and resource usage to the dashboard over a persistent GraphQL WebSocket connection. Updates appear in under a second — no polling, no refresh — and the same pipeline drives the alert system, so the data you see in the dashboard is the data your alerts evaluate against.
Real-Time Status via WebSocket
The bot status and metrics update in real time via GraphQL WebSocket subscriptions. The page does not need a refresh — changes push as the trading engine emits them.
Monitored in real time:
- Bot status (running, stopped, error, unhealthy)
- CPU and memory usage on the runner
- PnL changes as new trades close
- Trade lifecycle events (open, close, cancel, warnings)
- Strategy heartbeats (active trade count, current timeframe)
Analytics Dashboard
The Analytics tab on the bot detail page shows:
Performance Metrics
| Metric | Description |
|---|---|
| Total Profit % | Overall return since bot started |
| Total Profit (absolute) | Return in stake currency (e.g., USDT) |
| Trade Count | Total number of closed trades |
| Win Rate | % of trades that closed profitably |
| Profit Factor | Gross profit ÷ gross loss |
| Expectancy | Average expected return per trade |
| Max Drawdown | Largest loss from a peak |
| Best Pair | Highest-performing trading pair |
Time-Based P&L
View profit broken down by:
- Daily P&L
- Weekly P&L
- Monthly P&L
Open Positions
The Open Positions tab shows all currently active trades:
| Column | Description |
|---|---|
| Pair | Trading pair (e.g., BTC/USDT) |
| Direction | Long or Short |
| Open Rate | Price when the trade was entered |
| Current Rate | Current market price |
| Amount | Trade size |
| Unrealized P&L | Current profit/loss if trade were closed now |
| Duration | How long the trade has been open |
Resource Usage
The Usage tab shows infrastructure resource consumption:
- CPU Usage — Time-series chart of CPU utilization
- Memory Usage — RAM consumption over time
- Network I/O — Data sent/received
This helps identify if your runner needs more resources.
Price Chart
The Price Chart tab shows:
- Live OHLCV candlestick chart for your bot's trading pair
- Entry/exit markers showing where trades were opened and closed
- Key indicator overlays
Pair Performance
The Pair Performance tab shows a breakdown of performance by trading pair:
- Total profit per pair
- Trade count per pair
- Win rate per pair
This helps you identify which pairs are contributing positively or negatively.
FreqUI Access
For advanced monitoring, VolatiCloud integrates with FreqUI — Freqtrade's official web interface:
- Click the FreqUI button on the bot detail page
- A drawer opens with the full FreqUI interface
- Access advanced features like trade history, profit chart, performance stats, and configuration viewer
FreqUI access uses secure token-based authentication — your exchange API keys are never exposed in the browser.
Setting Up Alerts
For proactive monitoring, set up alert rules on your bot:
- Go to the Alerts tab on your bot page
- Create rules for events like:
- Bot status changes (error, stopped)
- Trade closed
- Large profit or loss
- Drawdown threshold reached
See Alert Rules for detailed configuration.
Bot Health Indicators
| Indicator | What to look for |
|---|---|
| 🟢 Running | Bot is healthy and trading |
| 🟡 Unhealthy | Bot running but health checks failing — investigate |
| 🔴 Error | Bot crashed — check logs and restart |
| ⚫ Stopped | Bot is inactive — no trades being made |
Troubleshooting Common Monitoring Signals
Bot shows error status
- Check the runner logs for detailed error messages
- Verify your exchange API keys are valid and have the right permissions
- Ensure the exchange isn't reporting downtime
- See the bot lifecycle docs for the recovery state machine
No trades being opened
- Verify the strategy's entry conditions are firing on current market data
- Confirm sufficient balance on the exchange for the configured stake amount
- Check that the trading pairs are active and have volume during the window
- For mean-reversion strategies, the market may simply not be in a state the strategy targets
High CPU/memory usage
- Consider a larger runner (or self-hosted runner) — see self-hosted vs cloud runners
- Reduce the number of pairs the bot monitors
- Simplify the strategy's indicator calculations or increase the timeframe
Related
- Bot lifecycle — state transitions and recovery
- Real-time bot monitoring blog post — what the WebSocket pipeline pushes and why
- Intelligent alerts — configure email/webhook alerts on the same event stream