Yeah the output on refresh doesn't list current reported hashrate at the end (refresh is the equivalent of hitting 's' in the console of the miner). However, the reported GPU hashrate and shares do show in the log every 5 seconds. If you pull the data at an interval greater than 5 seconds you should be able to grep the gpu reported hashrate and shares 10 or so lines up.
Alternatively, JSONRPC works if you script it into your code. It is universal between Phoenix and Claymore so it should keep your code small as there would be no need to have different code for each miner. This can be achieved with netcat:
Problem is that json-rpc requires Ethman.exe which is only available on Windows. I figured out a way and am almost done with the development so I'll stick to the html output.
Im not sure that it does. I just ran the commands fine without having ethman running on one of my miners and it responded just fine.
check out dev version 2.1.d8
There a a few things that are not clear to me with regards mapping the son fields to the influxDB fields. FYI, I try to map to existing one for consistency and ability to do cross-miner reporting
"hr": json.TotalHashRate, //this is the instant HR
"avg_result_time": json.TotalHashRateAvg, //This seems to be the average HR since miner started
"target_hr": r.TargetHashRate,
"shares_total": json.Shares.NumAccepted + json.Shares.NumRejected + json.Shares.NumInvalid + json.Shares.NumNetworkFail + json.Shares.NumOutdated,
"valid_shares": json.Shares.NumAccepted,
"invalid_shares": json.Shares.NumInvalid,
"stale_shares": json.Shares.NumRejected, // Are these rejected by the pool?
"outdated_shares": json.Shares.NumOutdated, // are these stale shares i.e. shares submitted and block has been closed and a new block generated?
"networkfail_shares": json.Shares.NumNetworkFail, // have no idea about these
Let me know if that's ok with you or if I should do some re-mapping