I’ve got a map operation that attempts to remove an entry from a bin of type Map. In case the record doesn’t exist I contract an exception with error code
Such a scenario is normally acceptable from my business case perspective, so my app catches the error and proceeds.
The only obstacle I face at the moment is a monitoring system which alerts me every time the server-side metric
client_write_error value increases.
According to the Knowledge Base, there are a number of reasons for the metric value to grow. And it would be a bad idea not to monitor its value completely.
Is there a way to ask a server not to fail the request when a record doesn’t exist and not to increment the client_write_error metric for the cases when I expect the operation to fail?
Is there a way to distinguish cases when something goes out of my control (like write_queue depth exceeded or record too big or stop wrights threshold exceeded etc…) and normal cases when I expect a failure to happen?
Would you please recommend the best practices to monitor this metric?