-
Notifications
You must be signed in to change notification settings - Fork 79
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
Create promrated utility to report validator metrics #1540
Comments
obol-bulldozer bot
pushed a commit
that referenced
this issue
Dec 13, 2022
Start of #1540. Per corvers suggestion taking incremental steps instead of a large code dump. This starts by reading the necessary config values, then runs on a loop every 10 mins with some logging. After this I will expose some metrics to prometheus then start some of the more complex logic for fetching clusters and polling rated. ticket: #1540 category: misc
obol-bulldozer bot
pushed a commit
that referenced
this issue
Dec 14, 2022
Start serving prom metrics at the specified address along with a health endpoint to use for a liveness check. category: misc ticket: #1540
obol-bulldozer bot
pushed a commit
that referenced
this issue
Dec 16, 2022
Adds fetching of rated effectiveness and making these metrics available to prometheus. category: misc ticket: #1540
obol-bulldozer bot
pushed a commit
that referenced
this issue
Dec 16, 2022
Adding build and deployment for promrated. Depends on ObolNetwork/obol-infrastructure#329 category: misc ticket: #1540
obol-bulldozer bot
pushed a commit
that referenced
this issue
Dec 16, 2022
Fixes location for binary category: bug ticket: #1540
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem to be solved
Currently we only have our own charon metrics being reported to prometheus. We would like to be able to see external performance metrics from rated in our dashboard also.
Proposed solution
Design doc
Create a utility tool in testutils. This will get all clusters that currently make their metrics available to our prometheus instance, and intermittently scrape the rated data for each pubkey. This data will then be labelled with the appropriate cluster information and be made available for prometheus polling.
The text was updated successfully, but these errors were encountered: