Request to add Error Code as a option for triggers and alerts

alexander.olson

I would like to suggest adding error codes as an option for alerts and triggers.

Currently, whatsminer miners with error codes can present as not having a pool or having an invalid pool. This can lead to false positives in detection and repeated reapplication of pool config to a miner that has a pool already. 

Adding error codes would allow for specifying miners with X Error code to help catch miners that are hashing to an incorrect pool while still being able to catch 2000 error codes for new miners that need config pushed to them. 

Would also be useful to catch other error codes in triggers such as overcurrent. 

3

Comments

2 comments

Date Votes
  • Comment author
    mcguire

    Error codes also need to be added to the miner table as an actual column, field as opposed to the weird mouseover-tag-thing that currently gets attached to miner name.  

    0
  • Comment author
    tcheek
    • Edited

    Hi Alexander, 

    Error codes are now actionable in Custom Issues and this quarter we plan on adding Custom Issues into our Alerts and Triggers. I think this could solve your problem. A good first step would be to create the custom issues for the specific error codes you're looking at and then we can look at getting those into alerts and triggers. Happy to find some time to discuss too.

    Thanks,

    Tim

    tcheek@obm.io

    0

Please sign in to leave a comment.