[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[patrike]

ConfigData.xml (located in %appdata%\AwesomeMiner\ folder) is the only configuration file for Awesome Miner. You can copy this one between your computers, but please make sure that Awesome Miner isn't running (Menu -> Exit) before you replace the configuration on the target computer. Can you please check this one more time?

I tried again with the same result.  Here's AM running on the source computer:

Size of the ConfigData.xml file is ~1,100 KB.

Here's what AM looks like after copying that 1,100 KB file to the target computer and waiting a couple of minutes :

So only miners that are working are the external ones.  None of the managed miners show up (they are still running).

Also, after running for a few minutes the size of the ConfigData.xml file is reduced to ~800 KB.

All the profit profiles and hosts are missing from the target computer after starting up AM there.  (which explains why they don't show up as running)  So this is likely what accounts for the ~300 KK worth of metadata that gets deleted from the xml file upon startup.  It is also interesting to note that the miner "antminer 103 - S9" is showing up on the target computer even though that was deleted from the source computer about a week ago.

Thanks for the update.

The miner lists are not the same, so the configuration must have been either loaded or taken from a backup file. Do you use the same version of Awesome Miner? Recent versions actually store the data a bit more efficient so they have smaller file size compared to older versions.

If Awesome Miner is unable to load ConfigData.xml, for example because of version incompatibilities, it will go for any of the backup files instead. I would suggest to first exit Awesome Miner completely on the target computer, then remove all files in the folder %appdata%\AwesomeMiner\, and finally put the ConfigData.xml in there and start Awesome Miner again. Then there are only two possibilities:
1) Either Awesome Miner load the exact content of ConfigData.xml and what you see on the screen is what the file contains
2) Or you will see a completely empty Awesome Miner window with no miners because it failed to load the configuration file.

Something in between is not possible.

Please also note that you cannot have two Awesome Miner main applications running at the same time controlling the same Remote Agents - that will result in miners showing up as stopped. It's only ASIC miners (External Miners) that can be monitored from multiple instances of Awesome Miner as the same time.

[1714710601]

1714710601

[1714710601]

1714710601

[1714710601]

1714710601

[soothaa]

Good morning Patrike quick question for you.

I am always on the bleeding edge of miners and using betas hours after they are released. When trying to benchmark many of them, I simply get a "unknown option --benchmark" message and then the software just mines on some random pool and usually the wrong algo (z-enemy) is the latest one doing this.

It would be really nice if the benchmark page could be reworked to have a dropdown to choose:

1) Select the software you wish to benchmark
2) Select the algo you wish to benchmark
3) The pool for a matching coin is selected from the profit switching section so I don't have to be constantly maintaining random pools for that info

This would be a huge help and improvement over the current dialog as it is not even sortable by software..

As always, thank you for your work!

In the recent versions of Awesome Miner, the benchmark dialog has a checkbox for "Benchmark without a pool". When checked, Awesome Miner will tell the mining software to run in benchmark mode when supported, which for some software results in adding "--benchmark" to the command line. If you uncheck this setting, the benchmarking will be using a pool and no "--benchmark" should be added.

Thanks for your feedback for the benchmark feature. These are good points and can for sure be input to future improvements.

Yes, this behavior is specifically when using that feature.

[soothaa]

Hi patrike,

I'm experiencing an issue mining with excavator through AM.

I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this

Code:

=========================== www.nicehash.com =========================
           Excavator v1.4.4a_nvidia GPU Miner for NiceHash.
           Copyright (C) 2018 NiceHash. All rights reserved.
                              Developed by
                djeZo, dropky, voidstar, and agiz
                   with help and contributions from
           zawawa, pallas, Vorksholk, bitbandi, ocminer, and Genoil.
=========================== www.nicehash.com =========================

Build time: 2018-02-16 13:11:25
Build number: 4645
Provided startup commandline:
        "C:\Users\MINEUR\AppData\Local\AwesomeMinerService\UploadedSoftware\excavator\excavator.exe"     -c awesome.json -p 4028

[05:05:15][0x00000fc0][info] Log started
[05:05:15][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] api | Listening on 127.0.0.1:4028
[05:05:16][0x00000fc0][info] core | Initialized!
[05:05:19][0x000007d4][warning] core | Command exec: invalid stoi argument
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy

The awesome.json file generated in excavator folder look like this

Code:

[
	        {"time":0,"commands":[
		        {"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","my.btc.address"]}
	        ]},
	        {"time":1,"commands":[
		        {"id":1,"method":"algorithm.add","params":["equihash"]}
	        ]},
	        {"time":3,"commands":[
		        {"id":1,"method":"worker.add","params":["equihash","0"]},
{"id":1,"method":"worker.add","params":["equihash","1"]},
{"id":1,"method":"worker.add","params":["equihash","2"]},
{"id":1,"method":"worker.add","params":["equihash","3"]},
{"id":1,"method":"worker.add","params":["equihash","4"]},
{"id":1,"method":"worker.add","params":["equihash","5"]},
{"id":1,"method":"worker.add","params":["equihash","6"]},
{"id":1,"method":"worker.add","params":["equihash","7"]},
{"id":1,"method":"worker.add","params":["equihash","8"]},
{"id":1,"method":"worker.add","params":["equihash","9"]},
{"id":1,"method":"worker.add","params":["equihash","10"]},
{"id":1,"method":"worker.add","params":["equihash","11"]},
{"id":1,"method":"worker.add","params":["equihash","12"]}
	        ]},
	        {"time":10,"loop":10,"commands":[
		        {"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"worker.print.speed","params":["6"]},
{"id":1,"method":"worker.print.speed","params":["7"]},
{"id":1,"method":"worker.print.speed","params":["8"]},
{"id":1,"method":"worker.print.speed","params":["9"]},
{"id":1,"method":"worker.print.speed","params":["10"]},
{"id":1,"method":"worker.print.speed","params":["11"]},
{"id":1,"method":"worker.print.speed","params":["12"]},
		        {"id":1,"method":"algorithm.print.speeds","params":["0"]}
	        ]}
        ]

I don't understand why there's this "invalid stoi argument"
Thanks !

I'm getting this as well.. I think something broke that miner in the CUDA 9.2 upgrade...

[dasch]

Hi patrike,

I'm experiencing an issue mining with excavator through AM.

I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this

It looks like Awesome Miner think you are using Excavator 1.5, as it will try to connect to "nhmp.eu.nicehash.com:3200". It might be the detection in Awesome Miner isn't perfect for this scenario. Do you want to use 1.4 or is 1.5 an option?

I prefer keeping 1.4 version so I can use any server and not only nicehash's one.

[crazydane]

If Awesome Miner is unable to load ConfigData.xml, for example because of version incompatibilities, it will go for any of the backup files instead. I would suggest to first exit Awesome Miner completely on the target computer, then remove all files in the folder %appdata%\AwesomeMiner\, and finally put the ConfigData.xml in there and start Awesome Miner again. Then there are only two possibilities:
1) Either Awesome Miner load the exact content of ConfigData.xml and what you see on the screen is what the file contains
2) Or you will see a completely empty Awesome Miner window with no miners because it failed to load the configuration file.

Something in between is not possible.

Please also note that you cannot have two Awesome Miner main applications running at the same time controlling the same Remote Agents - that will result in miners showing up as stopped. It's only ASIC miners (External Miners) that can be monitored from multiple instances of Awesome Miner as the same time.

I exited/stopped Awesome Miner on the target.

I deleted everything in %appdata%\AwesomeMiner\

I copied in the ConfigData.xml file

I started up Awesome Miner and get a completely empty Awesome Miner window now.  Source is running latest pre-release and Target is running latest release I was able to download, which is 3.3.3.  So I guess what I need to to is to manually register the version on the target and upgrade it to the latest pre-release and try again? (after clearing out %appdata%\AwesomeMiner\ again and copy in ConfigData.xml again)

EDIT:  I did what I suggested in the last paragraph and that did the trick!

[danieldaniel81]

Awesome miner is interesting , i use with miningpoolhub
You see other coins , temperature , FAN  ,

[darius510]

Is anyone else having any responsiveness issues with the latest release(s)? It seems like the UI locks up any time there's a large number of profit switches.

[moppidoo]

Is anyone else having any responsiveness issues with the latest release(s)? It seems like the UI locks up any time there's a large number of profit switches.

I was getting that when Windows went through Insider Preview latest fast ring build (with that huuuuuge Notepad upgrade) 2 or 3 weeks back. Couldn't figure out why everything goes stuttering from time to time until I decided to just roll back and stay with stable builds. (yes, initially I suspected and thought it was AM 5.3.x broke my system since stutter happens every time profit switching took place, but turns out it was bloody Microsoft in my case)

[NotFuzzyWarm]

@ patrike
Any chance you can can have the Avalons deliver full reports on each miner attached to their controller? Currently stats break down to each AUC device reporting the miners attached to it as 1 big miner.

The stats *are* in the api so here's the API log:

Awesome Miner is currently only displaying the information based on the devices in the API's. Each devices can then have 4 - 5 sub devices that is reported in a vendor specific way in these API's. Each of these sub devices represent a physical miner. With the current version of Awesome Miner, it uses the same device concept as for any other miner, and you might get 3 - 4 devices listed on the ASIC tab - even if the number of physical miners are 12 or more.

I would be possible for Awesome Miner to use the vendor specific information in the API's to dig deeper into the information and list all physical miners as a device on the ASIC tab - with individual hashrates and temperature information for each.

From a management point of view it's however still a only single large miner in Awesome Miner, as pool operations and similar are only set to the R-Pi controller. Each physical miner is only made available with monitoring information over the API's, but all of them are still controlled like single miner.

Controlled as a single miner yes but what we (including Phillipma and his client) would like is performance information on those sub miners vs performance of any of the 4 possible miner strings as a whole.

Case in point, today I noticed that 1 of my banks of A741's was about 2THs lower than its normal total average of ~41THs. Now that could be simple variance at work given the rather large total miner throughput reported so the drop was sustained for several hours before I caught it.

All AM tells us is that one of the strings is under performing but *not* which miner in the string. The Avalon API provides very fine-grained detail if desired but all we want is to be able to look at the individual miner GHs so we can then know which GUI address to open to dig deeper for more detail.

For me that is just an 'oh well open the 1 bookmarked link to the controller for 6 A741's I have to dig deeper".

For someone with a fully loaded controller running 20 miners from it (with 260THs possible from stock 841's) - even an entire single miner going down could for a time be viewed/treated as statistical variance. Finer reporting of each miner on any one of 100's of controllers is a necessity just to be able to more easily find which controller IP to open for the GUI.

The Avalon API has all that information there. Each miner stats starts with the tag DNA [miner_id] and that tag is a factory assigned Unique ID.

[darius510]

Is anyone else having any responsiveness issues with the latest release(s)? It seems like the UI locks up any time there's a large number of profit switches.

I was getting that when Windows went through Insider Preview latest fast ring build (with that huuuuuge Notepad upgrade) 2 or 3 weeks back. Couldn't figure out why everything goes stuttering from time to time until I decided to just roll back and stay with stable builds. (yes, initially I suspected and thought it was AM 5.3.x broke my system since stutter happens every time profit switching took place, but turns out it was bloody Microsoft in my case)

I havent changed anything about the OS. And this isnt a stutter, this is a full blown lockup for 5-10 seconds every minute. Like its not just annoying, its making the program almost unusable.

[jkminkov]

some of the new miners bundled with most recent version are screwing with the power limit set to 60% on my 1070, after a few hours I found that setting ignored and miner going on full power, any hint how to battle that horrendrous behavior, I can't pinpoint which miner does that because all work as expected with powerlimit 60%(set with afterburner upon boot in w10) until it goes wrong.

[moppidoo]

some of the new miners bundled with most recent version are screwing with the power limit set to 60% on my 1070, after a few hours I found that setting ignored and miner going on full power, any hint how to battle that horrendrous behavior, I can't pinpoint which miner does that because all work as expected with powerlimit 60%(set with afterburner upon boot in w10) until it goes wrong.

check if it's CryptoDredge, prior to 0.7.0, their DevFee sessions have (accused) been seen altering PL to 100%

0.7.0 and later doesn't do this anymore

[patrike]

@ patrike
Any chance you can can have the Avalons deliver full reports on each miner attached to their controller? Currently stats break down to each AUC device reporting the miners attached to it as 1 big miner.

The stats *are* in the api so here's the API log:

Awesome Miner is currently only displaying the information based on the devices in the API's. Each devices can then have 4 - 5 sub devices that is reported in a vendor specific way in these API's. Each of these sub devices represent a physical miner. With the current version of Awesome Miner, it uses the same device concept as for any other miner, and you might get 3 - 4 devices listed on the ASIC tab - even if the number of physical miners are 12 or more.

I would be possible for Awesome Miner to use the vendor specific information in the API's to dig deeper into the information and list all physical miners as a device on the ASIC tab - with individual hashrates and temperature information for each.

From a management point of view it's however still a only single large miner in Awesome Miner, as pool operations and similar are only set to the R-Pi controller. Each physical miner is only made available with monitoring information over the API's, but all of them are still controlled like single miner.

Controlled as a single miner yes but what we (including Phillipma and his client) would like is performance information on those sub miners vs performance of any of the 4 possible miner strings as a whole.

Case in point, today I noticed that 1 of my banks of A741's was about 2THs lower than its normal total average of ~41THs. Now that could be simple variance at work given the rather large total miner throughput reported so the drop was sustained for several hours before I caught it.

All AM tells us is that one of the strings is under performing but *not* which miner in the string. The Avalon API provides very fine-grained detail if desired but all we want is to be able to look at the individual miner GHs so we can then know which GUI address to open to dig deeper for more detail.

For me that is just an 'oh well open the 1 bookmarked link to the controller for 6 A741's I have to dig deeper".

For someone with a fully loaded controller running 20 miners from it (with 260THs possible from stock 841's) - even an entire single miner going down could for a time be viewed/treated as statistical variance. Finer reporting of each miner on any one of 100's of controllers is a necessity just to be able to more easily find which controller IP to open for the GUI.

The Avalon API has all that information there. Each miner stats starts with the tag DNA [miner_id] and that tag is a factory assigned Unique ID.

I understand your request and I do have one idea how to approach this. Right now the External Miner can represent a large number of miners for Avalon, for example 20 miners. The total hashrate as reported by the controller is what's being displayed and the ASIC tab only adds a bit more information (still not on the level of each miner, but for each chain of miners).

What I could do is to allow you to use multiple External Miners in Awesome Miner, where you configure each miner to represent a specific physical miner. From a monitoring point of view, this would then be 20 External Miners and you can see hashrates, temperatures and define rules that would operate on each single miner. If you would perform a pool change operation, it would however affect all miners on the same controller - unless there is some hidden feature on the controller to allow this to be performed on only a single miner.

The drawback would be that this approach would consume many more licenses in Awesome Miner, but it would be more similar to how the licenses works for all other ASIC miners. This would be up to each user of Awesome Miner to decide between the current and new approach:
1) Current: A single External Miner that is representing all miners on the controller. A single license allows many miners to be monitored.
or
2) New: Adding multiple External Miners, one for each miner. All 20 External Miners would have the same IP address, but a unique identifier on each to let Awesome Miner know which miner to present the information from. The only limitation for the moment are the operations that still only operates on the controller level.

Please let me know you view.

[patrike]

Is anyone else having any responsiveness issues with the latest release(s)? It seems like the UI locks up any time there's a large number of profit switches.

I was getting that when Windows went through Insider Preview latest fast ring build (with that huuuuuge Notepad upgrade) 2 or 3 weeks back. Couldn't figure out why everything goes stuttering from time to time until I decided to just roll back and stay with stable builds. (yes, initially I suspected and thought it was AM 5.3.x broke my system since stutter happens every time profit switching took place, but turns out it was bloody Microsoft in my case)

I havent changed anything about the OS. And this isnt a stutter, this is a full blown lockup for 5-10 seconds every minute. Like its not just annoying, its making the program almost unusable.

I've made a few optimizations in development version 5.3.10 that is about to be released. Once available, please upgrade and let me know if it's working better.

[patrike]

Awesome Miner Version 5.3.10 (Development preview of 5.4)

- Miner Tag trigger can be configured to trigger if a miner doesn't have the specified tag
- The profit switcher can be configured to ignore the current pool if the mining software crashed multiple times. Configurable via the Options dialog, Profit switching section.
- Improved threading performance when using larger number of miners and when executing commands on many miners at once
- Webhook actions can be configured for Basic Authentication
- WhatToMine custom URL's can point to sources with multiple coins
- Added execution option to run external commands as Administrator via the System tab
- Added option to reinitialize the GPU monitoring via the System tab
- Coins tab improved by separating Revenue and Profit into two separate columns that can be sorted individually
- Ensure miner hostnames cannot contain blank spaces
- Added variable support for webhook actions
- Disable MultiPool.us integration
- Zpool multiple region support
- Added YescryptR16 and Allium algorithms, including support in CpuMiner-Opt
- Use full paths when specifying configuration file to sgminer
- Improved support for custom mining software with download URL specified as part of profit profiles
- The download URL for mining software adds support for pointing to network file shares.
- Cloud Services update inteval configurable
- For Managed Profit Miners, only the active pools will be listed on the Pools tab.
- Removed old mining software: Excavator 1.1. The only supported versions from now on are Excavator 1.4 and 1.5.
- Added mining software: T-Rex nVidia GPU Miner
- T-Rex miner 0.5.6, including pool information when used as External Miner
- CryptoDredge 0.8.3
- Z-enemy Miner 1.15a with Hex algorithm support
- EWBF Equihash Miner 0.5
- SRBminer 1.6.5, including CryptoNight Red algorithm
- Correction to coins per day calculations for some algorithms like Blake 2b
- Correction to SRBMiner configuration file entries related to GPU settings
- Correction to hash rate for latest firmware versions of Innosilicon A9 Zmaster miner. If an older firmware is used for this miner, please upgrade to the latest firmware version.
- Correction to the content of the miner and pool notification messages if the mining process doesn't start correctly
- Correction to miner commands not being executed correctly if launched in a sequence via the rules
- Correction to incorrect display of first pool in list for some GPU mining software
- Correction to rule for executing SSH commands
- Correction to hashrate parsing for a few of the GPU mining software, where incorrect processing could result in no mining information being displayed
- Minor corrections

Items in blue are updated since the last development preview.

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates

Direct download links
http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
http://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

[joseph32]

- For Managed Profit Miners, only the active pools will be listed on the Pools tab.

Huge THANKS for this! 

[trucobit]

Hi all,

Just thought I would show off the web interface I made for Awesome Miner:
http://stats.finnsk3.com/

It uses the Awesome Miner API along with Nvidia-SMI and and API to my enphase solar controller.
I am also using a CLI based overclocking tool I wrote in C to apply my overclocks as I hate msi ab.

That's the public view, as I am authenticated I see stop,start,restart,reboot,set TDP,set overclocks buttons.

The rigs are all on TPLink HS100/HS110 smart power points and the interface monitors the rigs and if they are unreachable for 5minutes it turns the power point off, waits 30 seconds then turns it back on. All the rigs are set in bios to boot on power outage.

I have onpeak/offpeak power costing so during week days for 8 hours a day my power costs twice as much so my TDP limits are automatically heavily restricted during peak power cost.

When any of my 1080ti rigs start mining Ethereum it automatically launches the ethenlargement pill and closes it if they stop mining Eth.

If I launch discord or a game etc. on my main rig my monitoring script stop the rig from mining, set's my 1080tis TDP to 350w and sets my gaming clocks, resumes mining when I exit all games.

Scripts running on my server:


Now you have something to aim for Awesome Miner devs

You have thought about offering this service to third parties. You just have to make a website to sign up and add the API, and a recurring monthly payment from Paypal, I would pay $ 10 a month for having such statistics, and I know people from my telegram group who would also pay for that service.

You can offer a subdomain for each client only accessible by login. For me, it would be something that I have been looking for a long time. Only the number of switch changes per day in each machine would be missing.

[NotFuzzyWarm]

@ patrike
Any chance you can can have the Avalons deliver full reports on each miner attached to their controller? Currently stats break down to each AUC device reporting the miners attached to it as 1 big miner.
...

Awesome Miner is currently only displaying the information based on the devices in the API's. Each devices can then have 4 - 5 sub devices that is reported in a vendor specific way in these API's. <snip>

Controlled as a single miner yes but what we (including Phillipma and his client) would like is performance information on those sub miners vs performance of any of the 4 possible miner strings as a whole.<snip>

I understand your request and I do have one idea how to approach this. <snip>
The drawback would be that this approach would consume many more licenses in Awesome Miner, but it would be more similar to how the licenses works for all other ASIC miners. This would be up to each user of Awesome Miner to decide between the current and new approach:
1) Current: A single External Miner that is representing all miners on the controller. A single license allows many miners to be monitored.
or
2) New: Adding multiple External Miners, one for each miner. All 20 External Miners would have the same IP address, but a unique identifier on each to let Awesome Miner know which miner to present the information from. The only limitation for the moment are the operations that still only operates on the controller level.

Please let me know you view.

License option #2 is perfectly fine with me. As you said, it more accurately reflects the number of actual miners being monitored & controlled and is no different than when I used to run a bunch of S9's before replacing them with the Avalons.

In the case of Philipma1957 and his client with several 100's of controllers/thousands of miners that would obviously be a negotiated contract between you and them even under the current setup

The Avalon API does give rather granular control over the individual miners. Each controller can only point all attached miners to 1 pool along with the global reboot and stop/start/restart cgminer commands. However, also each sub miner can be individually soft rebooted. That would be a nice touch to have vs rebooting all miners on the controller. With up to 20 miners currently giving up to 260THs per controller seems silly to reboot the entire block just to give 1 miner a kick in the pants...

[ccgllc]

I'd also be fine with burning extra licenses.  This is in-line with what we discussed several months ago.

Cheers!

[Finnsk3]

You have thought about offering this service to third parties. You just have to make a website to sign up and add the API, and a recurring monthly payment from Paypal, I would pay $ 10 a month for having such statistics, and I know people from my telegram group who would also pay for that service.

You can offer a subdomain for each client only accessible by login. For me, it would be something that I have been looking for a long time. Only the number of switch changes per day in each machine would be missing.

I work as a full time back end web developer so I don't have a lot of time left but I will consider it.

The number of switch changes is actually something I am working on. I am going to implement a timeline showing what each rig is mining, how many swaps there are etc. I have been logging all this info to my DB, I just need to write the front end graphs.