Trade Journal And Export
The trade journal is the live-history surface of the product. It answers a different question from a backtest report: not what the strategy could have done historically, but what positions and fills were actually recorded for your bots.
What this is
This article explains how to use the current Trade Log tab in the Metrics workspace and how to export the recorded data.
When to use it
Use this article if:
- you want to review live or recorded positions
- you need to audit fills, fees, and hold duration
- you want to export journal data to CSV
Before you start
Important current product behavior:
- the Analytics workspace has two tabs: Metrics and Trade Log
- the page can be filtered by one bot or by All Bots
- the page auto-refreshes while visible
- the on-screen journal is for interactive review, while CSV export is better for wider analysis
Step by step
Step 1: Open the Trade Log tab
Go to Dashboard -> Analytics and switch from Metrics to Trade Log .
You can also open it directly from bot actions where the UI links to the trade-log view for that bot.
Step 2: Choose the right scope
Select:
- one bot, if you are debugging one strategy
- All Bots , if you want a portfolio-level review
When you use All Bots , the journal and the export can include bot identity in the output.
Step 3: Filter the positions
The current journal filters include:
- quick periods such as 7 , 30 , and 90 days
- start date
- end date
- symbol
- status ( open or closed )
Use filters before exporting so the file matches the question you are trying to answer.
Step 4: Read the summary cards
The current Trade Log tab summarizes:
- total positions
- win rate
- total PnL
- average hold duration
Use this summary for orientation, then move into the rows for actual diagnostics.
Step 5: Expand positions to inspect fills and fees
Each journal row gives core facts such as:
- symbol
- side
- status
- open time
- close time
- duration
- PnL
- trade count
Expand a row to inspect deeper details such as entry price, exit price, quantity, fees, and execution history.
Step 6: Export CSV when you need wider analysis
Use Export when you need:
- off-platform analysis
- archive snapshots
- a larger dataset than the on-screen view is comfortable for
In the current UI, the exported file uses the pattern steadyedge-trade-log-YYYY-MM-DD.csv .
What you should see
By the time you finish the journal review, you should have:
- the right bot scope selected
- filters that match the question you are analyzing
- a clear view of positions, fees, and holding time
- a CSV export when deeper external analysis is needed
Common mistakes
- reviewing all bots when the issue belongs to one specific bot
- forgetting to filter by date and drawing conclusions from mixed periods
- treating the top summary cards as enough detail
- ignoring expanded execution history when investigating execution quality
- expecting the on-screen list to replace a proper CSV export
Related articles
- How To Read Backtest Report
- Save, Edit, Clone, And Launch
- Bot Statuses And Status Reason