You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.
For each method the grpc_server_handled_total exposes currently ~17 labels, per each status code. In most cases having just SUCCESS / FAILURE distinction would be enough, and would reduce amount of exported labels, which maybe an issue in case of multiple rpc methods.
For a single data point, imagine a server with 20 RPC methods, each replica will then exports about 400 labels just for RPC statuses.
This 17 labels looks like on par with histrogram metric, that has option to disable it because of the cardinality issue.
The text was updated successfully, but these errors were encountered:
Got it. I think that request is reasonable, however, keep in mind that we are in the process of reworking this project (RE: #91), and as a result we are unlikely to accept PRs that are not bug fixes. That said I think this would be an amazing addition to the reworked version! :) cc @bwplotka
For each method the
grpc_server_handled_total
exposes currently ~17 labels, per each status code. In most cases having just SUCCESS / FAILURE distinction would be enough, and would reduce amount of exported labels, which maybe an issue in case of multiple rpc methods.For a single data point, imagine a server with 20 RPC methods, each replica will then exports about 400 labels just for RPC statuses.
This 17 labels looks like on par with histrogram metric, that has option to disable it because of the cardinality issue.
The text was updated successfully, but these errors were encountered: