-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add Mining Overview Dashboard #10
Comments
Could you elaborate? Is this about cross-miner reporting, miner+pool reporting or something else? |
yes, let's say a dashboard that informs the general status of the mining operation, compact, simple but the most important information being shown if there are 2 pools, 3 coins being mined,2 mining software being used the dashboard should show the stats about the general status of the mining operation. Maybe something like this to know that is happening to rigs Rigs Info: online/offline, gpus online/gpus installed, current hashrate, pool working for, gpus temp, gpus fan, power consumption And for some more detail these are some ideas about what could be, it's similar to dashboard mining overview from rig-monitorv1 -Profitability info: -Coins+Miner Info: for each coin: -Power info: -Pools Info: for each pool: This is just an idea of having a dashboard to see everything, maybe not as detailed but knowing if the operation is going well or there is a major problem with certain rigs |
Thanks for the input. I'll make sure I'll cover this once I have some time. |
Take a look at this one. I build it for some of my miners using xmr-stak. xmr-stak API does not provide the fan&temp KPIs, but that's easy enough to copy from some of the other templates. |
I am closing this for now. I'll add the profitability panels once they are finalized |
profitability will have how much electricity will cost for that month and how much profit will make so this is going great and can be closed because profitability is a feature in development thanks |
No description provided.
The text was updated successfully, but these errors were encountered: