gRPC statusCode tag should be integer
See original GitHub issueThe problem
grpc.*.processing.duration
timers have a tag, statusCode
, which is the name of enum Status. The name is misleading because the tag value is a string, not an integer code. It is also difficult to use the string value for automated alerts (raise hell if 75% of calls failed in the last 30 minutes). There’s no easy way to differentiate failed status codes from good ones without complicated regex that many alerting systems don’t support.
The solution
statusCode
should be the integer value of the status. Only 0
(OK
) and 1
(CANCELLED
) are good statuses, which makes it very easy to find all failed calls (> 1).
Please add a tag status
, the value of which will be the enum name; change statusCode
to be the integer value of the enum.
Alternatives considered
None exists.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
I’ve already done the research, and posted the link above, and not asking for help on that. It goes to show that your earlier comment “modern monitoring systems are either capable of remapping or checking for multiple values” isn’t true, so this ticket was closed prematurely on invalid grounds.
That said, I understand OSS doesn’t come with any guarantees, so I’m going to find a way around without support from the library. Thanks.
Sorry, but I cannot help you with that. Please search for the proper syntax for your chosen system yourself. The online documentation or SO can probably help you way better with that setup than I currently can. If such a feature is not supported by that system, you should consider using one, that offers what you need.