Request to add Error Code as a option for triggers and alerts Completed
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.
Comments
7 comments
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.
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
Error codes are now their own column in the miners table too mcguire
Yes, which is nice.
Unfortunately, not text searchable and filter access is still miserable.
Hi Matt,
Do you mean text searchable via the browser or search in Foreman? Yes, filtering on the miners table can be improved and we are working toward it as we move more pages over to our new tech stack, like the tickets table. We are working on the miners table now and hope to have it done soon.
Tim
Searchable in the foreman miner list. There's not really a good way to do anything with error codes except filter and add tags that can trigger actions. And filter requires manually typing, adding one error code at a time. Creating a filter to match a group of error codes, eg "540 and/or 541 and/or 542" should be very basic, but is awkward if possible at all.
The tech stack, style templates used in triggers, power management, etc is horrible and borderline unusable. Hopefully you're not going to totally break the miners table
Hey Matt,
I'm going to shoot you an email to find some time to meet one on one to better understand you concerns.
Thanks!
Please sign in to leave a comment.