Repository navigation
Dashboard at glance #2565
Description
Is your feature request related to a problem? Please describe.
Partially,
-
in the 'bot comparison' window you have a sum of all columns except the 'Balance'.
It could be cool to have that to know what is our current global capital.
We have to do the operation by hand and with a lot of bots it's quit difficult -
You recently added the very interesting 'Status' column (Dry, Live, Offline), which could also be very useful as a global selector.
Let me explain, with a selection header, clicking on the header would switch from Status-all to -dry then to -live then -offline, allowing you to select the bot group in one click -
For the last one, it's a little more complex: add a 'W/E', 'Warning/Error' column that would display the number of lines in the bot's log file from a grep -i 'warning' or 'error'.
The grep would be performed on a window to be defined (say, the last 100 lines of the file or the current date). The idea behind it is to have a dashboard that provides vital information at a glance.
Describe the solution you'd like
A clear and concise description of what you want to happen.
- Just the sum of the 'Balance' columns likes others columns
- Use a quick selector based on bot status to see Gains/Lost/Balance between Live and Dry bots
- Add crutial healthy Column info on # of possible Warn/Error
Describe alternatives you've considered
- Sum Balance by hand give me too often headache
- Check box bot one by one could be hard operation when you manage an army of
- I need to select the bot , one by one, first, then go to logs tabs and make a search in page browser to see if you have warn or error words
or launch terminal session and use a parallel-ssh to exec grep on all physical server on all logical bot log files. I prefer this one to get global info that say 'Today no Warn, No error', no need specific operation management just concentrate to your new start.
PS: If you implement 3. Don't forget to sum also # Warn/Err if sum = 0 then just concentrate to your new start.
I can give you the shell script of parallel-ssh if you want.
And finally...
Just to thank you for the impressive work you've done on Freqtrade family and its evolution.
Activity
xmatthias commentedon Sep 15, 2025
as for 1 - the balance is already there - but intentionally not part of the summary column.
Why? because we'd potentially aggregate
Suggest solutions to this (these were the blockers for it when implementing this initially - and still are) - and i'm happy to look at it.
for 2: logs don't see where to place that (physically). Room is already tight, especially if you got tons of bots in one "element".
we'd look at a dropdown menu - but placing this in a header is not gonna work as it'll increase the height of the header (already tried that - UX is very bad).
Again here - if you have some "UI/UX" ideas (where to place the functionality) - i'm happy to look at it.
3 is ... simpler than you might think - but it'll (severily) increase traffic, as logs are not fetched in the background by default.
I'd also have it use all available logs - which is at max. the last 1000 rows on a running bot.
Using just the last 100 won't help much - as you can't tell if 100 lines is 1 minute, or 2 days (which can also change VERY quickly) - so every timerange we'd select here is pretty much arbitrary.
bigbroseur commentedon Sep 15, 2025
2 add in frequi setup menu, default currency USDC/T, BTC and convert with a rate on hourly or daily basis (just an estimate)
Yes, you'r right it's not easy to determine an accurate way to get the info.
With the heartbeat (live, dry, offline) implementation, you cannot add an internal flags err , warn, reset at each heartbeat and send it with the heartbeat status.
About UI/UX, add a small green orange red colored tablet to the status bot, green nothing , orange (got warns ), red (error message) no need numbers just colored tablet/flags.
xmatthias commentedon Sep 16, 2025
Well this ignores the difference between live and dry bots.
a sum of 10000$ (as mentioned above) consisting of 9000$ dry, and 1000$ live - makes the 10_000$ sum irrelevant / pointless, doesn't it?
for 2 - i guess you don't have an idea on where to place it either 😆 which confirms my doubts on "how" 😆
I think allowing to click the button might work - so i'll try that for now.
feat: Allow bot-selection by clicking the the live/dry badge
bigbroseur commentedon Sep 16, 2025
Here is what it could be (global selector + err/warn flag) :
All = Summary check
Live = Summary uncheck + all Live check
Dry = Summary uncheck + all Dry check
You can also add selector to balance:
feat: Add aggregated balance to bot-comparison
xmatthias commentedon Sep 19, 2025
the first 2 points are now somewhat implemented.
the 3rd (the logs) - i'm not convinced on it's use - and concerned on fetching logs too frequently - so i don't plan on adding this soon.
i may give it a try to see impact - which could also lead to the rejection of this 3rd part - but again - no plans on doing that soon.
bigbroseur commentedon Sep 20, 2025
Hello Matthias,
To avoid network saturation, perhaps we can handle only 2 flags errors, warns, handles by loggers set to 1 and reset between each heartbeat. The heartbeat will send then only this 2 flags to frequi.
Also no more need small green orange red colored tablet to the status bot but only change the background color of the bot status 'dry' or 'live' (green = ok, orange = warns, red = errors ).
HTH