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.

Sign up for GitHub

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

Jump to bottom

Track duty failing reasons on aggregate dashboard #1382

Closed
corverroos opened this issue Nov 3, 2022 · 0 comments
Closed

Track duty failing reasons on aggregate dashboard #1382

corverroos opened this issue Nov 3, 2022 · 0 comments
Labels
enhancement New feature or request protocol Protocol Team tickets

Comments

@corverroos
Copy link
Contributor

Problem to be solved

We would like to know "why" duties are failing on a the centralised aggregate metrics level. This would allow us to identify changes in duty failing trends, i.e., if there is a huge increase (or decrease) in some reason, then we should be able to identify and explain it.

This information is however only available in logs, not in metrics.

Proposed solution

Two options:

  • Add centralised log store (requires a lot of work)
  • Refactor current tracker failed_msg from a string into a enum (number) and add that as label to failed_duty_counter.
@OisinKyne OisinKyne added the enhancement New feature or request label Jan 16, 2023
@thomasheremans thomasheremans added the protocol Protocol Team tickets label Jan 23, 2023
@corverroos corverroos mentioned this issue May 26, 2023
Merged
obol-bulldozer bot pushed a commit that referenced this issue May 26, 2023
@corverroos
core/tracker: instrument structured reasons (#2242)
f307712 
Refactors tracker failed reasons into structured data and add metric to track failed reason codes.

category: refactor
ticket: #1382
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request protocol Protocol Team tickets
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@OisinKyne @corverroos @thomasheremans