Collect faulty validator indexes in Prometheus labels #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adaszko
changed the title
|
This might kill our Prometheus. :) Visualizing all these metrics is also a challenge. Can you try logs-based metrics instead? |
|
I'd also strongly recommend making it turnable via CLI. Other users might want to see all these metrics. |
|
Yeah, you're probably right. I'm gonna park this for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It would be more straightforward to collect validator public keys, but they take up a lot more spaces than indexes in the prometheus database. Indexes are quite easily mappable to validator public keys anyway.