-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Observer to ignore unhandled debug event types #14589
Conversation
Commit 24573e70a94d0aed647a6bf06b45e6b0961ed985 does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
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.
Support for both in the observer should land soon, but I agree that we should not spam the debug messages with this.
Edit: Please don't forget to sign-off your commit.
24573e7
to
91850ba
Compare
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.
Instead of &&
condition on an if, it would be better to call out a separate inner if with just that condition and explicit continue with a comment explaining why it's silenced.
When running cilium-agent in debug mode, the cilium-agent will throw tons of logs which looks like this: ``` level=debug msg="failed to decode payload" error="can't decode following payload type: 2" ``` Type 2 means MessageTypeDebug. Similarly Type 3 MessageTypeCapture also has similar issue. They are only for debug, so ignore the them from local observer. Signed-off-by: Yongkun Gui <[email protected]>
91850ba
to
626b8ed
Compare
updated. actually, I don't quite understand the difference between unknown event type and invalid event type. They look the same to me.. |
test-me-please |
When running cilium-agent in debug mode, the cilium-agent will throw
tons of logs which looks like this:
Type 2 means MessageTypeDebug. Similarly Type 3 MessageTypeCapture also
has similar issue. They are only for debug, so ignore the them from local observer.