-
Notifications
You must be signed in to change notification settings - Fork 482
fix(conn): update no-op logger to scheduler logger #656
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -192,6 +192,8 @@ type Handshaker struct { | |
| networkEvents networkevent.Producer | ||
| peerID core.PeerID | ||
| events Events | ||
|
|
||
| logger *zap.SugaredLogger | ||
| } | ||
|
|
||
| // NewHandshaker creates a new Handshaker. | ||
|
|
@@ -223,6 +225,7 @@ func NewHandshaker( | |
| networkEvents: networkEvents, | ||
| peerID: peerID, | ||
| events: events, | ||
| logger: logger, | ||
| }, nil | ||
| } | ||
|
|
||
|
|
@@ -359,5 +362,5 @@ func (h *Handshaker) newConn( | |
| isPeerOrigin, | ||
| info, | ||
| openedByRemote, | ||
| zap.NewNop().Sugar()) | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why did we have a no-op logger in the past and are we 100% sure that we didn't miss any logs (that we shd move from Info/Error to Debug) that this logger is used for?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It looks like it was refactored but never wired up correctly. The logger is only used for the four logs that this PR touches. |
||
| h.logger) | ||
| } | ||
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.
this log tends to show up A LOT for the origin. It's one of our most common logs that we have. I have 2 concerns:
WDYT?
Uh oh!
There was an error while loading. Please reload this page.
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.
nocollectrule on the agent's scheduler logs, so we can let it soak without spiking log ingestion rates.INFO, as this is more appropriate thanERROR.