feat: integrate Grafana Alloy and Loki for metrics and logging#11189
Open
Dyslex7c wants to merge 2 commits intoNethermindEth:masterfrom
Open
feat: integrate Grafana Alloy and Loki for metrics and logging#11189Dyslex7c wants to merge 2 commits intoNethermindEth:masterfrom
Dyslex7c wants to merge 2 commits intoNethermindEth:masterfrom
Conversation
This file contains hidden or 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.
Changes
scripts/monitoring/alloy-config.alloy- Grafana Alloy configuration that collects Nethermind container logs via the Docker socket and forwards them to Grafana Loki, and scrapes Nethermind Prometheus metrics (port 8008) and forwards them to Grafana remote write endpointsync-supported-chains.ymlto start Grafana Alloy as a Docker sidecar after Sedge brings up the Nethermind node, and stop it gracefully before VM teardown to ensure buffered logs and metrics are flushedjob,project,external_provider,Instance,Network,User) to ensure consistency with the Alloy integration inpost-merge-smoke-testsTypes of changes
What types of changes does your code introduce?
Testing
Requires testing
If yes, did you write tests?
Documentation
Requires documentation update
Requires explanation in Release Notes
Remarks
cc @cbermudez97 for review