Describe the bug
A lot of times when events are sent from trigger to the service, they receive a response code of 0, which indicates there was no response (possibly due to a timeout?). We don't have a response_code_class for this, and thus a NULL value is stored as the class which can get a bit confusing especially when querying metrics and calculating things like events throughput.
Expected behavior
It'll be great to have a response_code_class associated with a response code of 0 to be certain of what happened to the event when seeing the response code class.
Describe the bug A lot of times when events are sent from trigger to the service, they receive a response code of 0, which indicates there was no response (possibly due to a timeout?). We don't have a response_code_class for this, and thus a NULL value is stored as the class which can get a bit confusing especially when querying metrics and calculating things like events throughput.
Expected behavior It'll be great to have a response_code_class associated with a response code of 0 to be certain of what happened to the event when seeing the response code class.