-
Notifications
You must be signed in to change notification settings - Fork 95
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
app: eth2wrap latency logging #3417
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3417 +/- ##
==========================================
- Coverage 57.36% 57.28% -0.09%
==========================================
Files 217 217
Lines 31977 31977
==========================================
- Hits 18345 18319 -26
- Misses 11744 11766 +22
- Partials 1888 1892 +4 ☔ View full report in Codecov by Sentry. |
67e4662
to
2cd6fe0
Compare
Quality Gate passedIssues Measures |
log.Debug(ctx, "Beacon node call finished", z.Str("endpoint", endpoint)) | ||
// If BN call took more than 1 second, send WARN log | ||
if rtt > time.Second { | ||
log.Warn(ctx, "Beacon node call took longer than expected", nil, z.Str("endpoint", endpoint), z.Str("rtt", rtt.String())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we see this warning even when enableLogs
is disabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shall probably discard this work entirely in favor of #3429
Adding logs for some beacon node calls RTT. In order to help tracking issues with underperforming beacon nodes, caused either by slow infrastructure/networking or issues from the beacon node itself.
Currently logs have been added only on the calls for:
I'm open to including more endpoints.
Fixing linter on one place.
category: feature
ticket: none