FEAT: Add per chain and node metrics #198
Closed
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
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.
Summary
This Pull Request introduces per-chain and per-node metrics collection into the Horcrux monitoring system. The main objective of this update is to enhance system observability, enabling a deeper insight into the individual performance of each node and chain. This is instrumental for network health assessment, debugging, and performance optimization.
Background
Prior to this PR, Horcrux only provided global metrics which made it challenging to debug issues on a per-node or per-chain basis. As Horcrux networks can be composed of multiple chains and nodes, a granular level of metrics is essential for operational excellence.
Changes
As this is an extension of the existing metrics collection, it does not require special migration steps. However, due to the label changes, ensure compatibility with dependent services and tests.