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

Distinguish between "not readyz reasons" #999

Closed
corverroos opened this issue Aug 19, 2022 · 0 comments
Closed

Distinguish between "not readyz reasons" #999

corverroos opened this issue Aug 19, 2022 · 0 comments
Assignees
@corverroos

Comments

@corverroos
Copy link
Contributor

corverroos commented Aug 19, 2022 •
edited
Loading

Problem to be solved

Currently, the app_monitoring_readyz only distinguishes between ready (1) and not ready (0).

It is however very helpful to users to know whether their beacon node is down vs peers are down as different actions are required.

Proposed solution

Distinguish between different values for app_monitoring_readyz:

  • 0: unset
  • 1: ready!
  • 2: beacon node down
  • 3: insufficient peers

Out of Scope

We might need to add some kind of "beacon node score" metric which indicates how good your beacon node is, since that is the main thing affecting performance. We can do something with bn_error_count and bn_latency and create a score out of 100?
@corverroos corverroos mentioned this issue Oct 17, 2022
Merged
obol-bulldozer bot pushed a commit that referenced this issue Oct 17, 2022
@corverroos
app: instrument not ready reasons (#1302)
952e371 
Instruments not ready reasons for improved UX. 
Also fix a "concurrent map write" panic in peerinfo.

category: feature 
ticket: #999
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@corverroos corverroos

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@corverroos