feat: introduce aggoracle metrics #1187
Merged
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
Stefan-Ethernal
force-pushed
the
feat/introduce-aggoracle-metrics
branch
from
355edcd to
ed63fed
Compare
|
goran-ethernal
approved these changes
Oct 31, 2025
temaniarpit27
approved these changes
Nov 3, 2025
| go func() { | ||
| start := time.Now() | ||
| err := a.chainSender.ProcessGER(ctx, latestGER) | ||
| metrics.ObserveGERProcessDuration(time.Since(start)) |
Contributor
There was a problem hiding this comment.
should we also track which ger took how much time? wdyt?
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 Summary
This PR introduces the following Prometheus metrics to the
aggoracle.aggoracle_ger_processing_trigger_totalaggoracle_ger_processing_errors_totalaggoracle_ger_processing_duration_secondsN/A
📋 Config Updates
N/A
✅ Testing
🐞 Issues
🔗 Related PRs
N/A
📝 Notes
N/A