1) It's only possible to initiate the connection from Awesome Miner to Remote Agent. It's quite common to setup VPN solutions for these scenarios. In the future, it will also be possible to use the Cloud Services to solve these networking scenarios.
2) You will find the CPU / GPU information on the System tab at the bottom of the screen for the selected miner. This information is always available, even when no API is available or the mining process is stopped
3) The rules doesn't support the concepts of GPU load and Internet connection. The GPU load reported by the system isn't always an accurate way to know if the system is performing well.
If you are running with the profit switcher, you can enable "Ignore pools with no accepted shares" in Options dialog, Profit switching section. Then Awesome Miner will automatically change to another pool in case the first isn't performing as it should. The pool will be marked as failed for the number of miners you have configured, and then it will be used again.
You can have a similar setup with the predefined rule "Accept Progres" in Options dialog, Rules section, where you can take action in case the miner isn't making any process on the hashing or the mining pool is down. In this scenario there are however no way of automatically adding back the first pool once available again.
2) Yes I know it's there. But why not to show it on dedicated tab? If I have rigs with supported miners and without them - it would be better to see all needed info without switching tabs.
3) OK. Is there any way to run a simple script, that will return some value and then do some action based on that value?
(For example to run nvidia-smi - get GPU load - calculate average and return it to AM, so that AM could switch/restart the miner.
4) No. I don't need profit switching. But I need to make sure that rigs are working and correctly respond to different troubles automatically.
a) miner crashing. Count number of restarts and if it is greater than 2-3 within 2-3minutes switch to failover mining list.
b) miner hanging and doing nothing. Get GPU load and if idle for 2-5minutes switch to failover mining list.
b) GPUs down. If down -> hardreset.
c) pool down.
d) internet down.
etc.
2) The GPU tab is currently based on the number of GPU's with their hashrates reported by the mining software. Without an API to the mining software this list will be empty as Awesome Miner doesn't know how many GPU's you are using.
Awesome Miner could of course be improved here by introducing some new concept where you can select how many GPU's to bring in via the existing feature "Map to system monitoring" for the scenario where no GPU's are available via the mining software.
3) This would be some custom implementation required. It's possible to control Awesome Miner from external scripts and application using the HTTP API:
http://www.awesomeminer.com/help/api.aspx4a) You can use the rule trigger "Process failure" with "Mining process not running and too many failed attempts to restart". This will trigger after 3 crashes within a short period of time. The number 3 can be configured via the Options dialog, Advanced section, "Restart attempts on process crash".
4b - 4d) "Accept progress" should find these. Except "GPU's down", where it will depend on if the mining software can report this correctly. If it can, the predefined rule "Dead device detection" can be used.