Skip to content
New issue

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

Metric broadcast_errors is not correctly batching the same errors together #3720

Closed
5 tasks
ljoss17 opened this issue Dec 5, 2023 · 0 comments · Fixed by #3719
Closed
5 tasks

Metric broadcast_errors is not correctly batching the same errors together #3720

ljoss17 opened this issue Dec 5, 2023 · 0 comments · Fixed by #3719

Comments

@ljoss17
Copy link
Contributor

ljoss17 commented Dec 5, 2023

Summary of Bug

The metric broadcast_errors introduced in Hermes v1.7.2 uses the error code and error description as label. The issue is that some error description have variables in them causing Hermes to consider them as different errors, for example it would record two separate metrics for due to the required fee being different:

broadcast_errors_total{account="<account_1>",error_code="13",error_description="insufficient fees; got: 1234stake which converts to 1234stake. required: 2345stake: insufficient fee"} 1
broadcast_errors_total{account="<account_1>",error_code="13",error_description="insufficient fees; got: 1234stake which converts to 1234stake. required: 3456stake: insufficient fee"} 1

Version

Hermes v1.7.3


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@ljoss17 ljoss17 changed the title Metric broadcasting_errors is not correctly batching the same errors together Metric broadcast_errors is not correctly batching the same errors together Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant