[Feature Request] Miner API calls

[roboyeti]

I am working on Signum integration into a soon to be available (and open source) monitoring app and just found the API for Btdex, which is great, except I don't see the real value of what is offered in it, since all of that data is available in explorer (except saving resources on those). What would be fantastic is if the client actually had API end points for the miner, allowing apps like mine to give users a remote view into the health of their mining rig(s).

[jjos2372]

Hello, it is actually wrapping https://github.com/signum-network/signum-miner, which is a command line tool.

Maybe another alternative is to extend the https://github.com/signum-network/signum-pool code to improve remote monitoring. Currently one can already monitor if the miner is running or not, but not much more than that.

[roboyeti]

Ya, I was just following the thread in the code and looking at the miner. I think it would be valuable to adopt some of the CPU/GPU miner mentality here, as most provide an API for monitoring, and these days, control. It would be nice to have a remote start/stop and at least a json of log lines being captured from the miner, maybe, which could be parsed by caller. I don't think it would make sense for Btdex to try and structure the console log output of the miner. The miner should probably offer up the API for that, which would be cool, because then smarter wrappers around the miner would be that much easier. For the time being, I am just going to provide a wrapper around the actual miner for those who want to remote montior. I already have what I could find from the pool ... unless there is more that I am missing (I don't really see a "running" option, but confirmations is what I check for):

Currently, I think what the pool shares makes sense for the pool, but would like to see the round times etc, which doesn't make as much sense in the pool data (maybe...), but it sure would be nice to have "reported physical" to compare drive size against calculated drive size ... for informational purposes only, obviously couldn't be "relied" upon.

Here is what I have now (and adding a Token monitor right now):