We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@kobayurii @telezhnaya I've talked to @gmilescu, who suggested we split the errors in the counters. Something like:
block_error_proxies_counter_0
block_error_proxies_counter_1
block_error_proxies_counter_3
This is similar to what @kobayurii did in #93 PR for separating logs. What do you think?
Originally posted by @khorolets in #93 (comment)
The text was updated successfully, but these errors were encountered:
I agree, but we should also add a fourth option block_error_proxies_counter_4 - RR error, AR error, data mismatch
Sorry, something went wrong.
refactor(rpc-server): Split error metrics to disambiguate the error r…
e0f82aa
…easons #97
d1707e6
…easons (#98) * refactor(rpc-server): Split error metrics to disambiguate the error reasons #97 * fix(rpc-server): README metric error codes fix grammar * Update rpc-server/README.md Co-authored-by: Olga Telezhnaya <olyatelezhnaya@gmail.com> --------- Co-authored-by: Olga Telezhnaya <olyatelezhnaya@gmail.com>
Successfully merging a pull request may close this issue.
@kobayurii @telezhnaya
I've talked to @gmilescu, who suggested we split the errors in the counters. Something like:
block_error_proxies_counter_0
- RR success, AR success - data mismatchblock_error_proxies_counter_1
- RR success, AR errorblock_error_proxies_counter_3
- RR error, AR successThis is similar to what @kobayurii did in #93 PR for separating logs. What do you think?
Originally posted by @khorolets in #93 (comment)
The text was updated successfully, but these errors were encountered: