-
Notifications
You must be signed in to change notification settings - Fork 260
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
Update debug/info logging levels used in Kafka Topic connector #6858
Comments
cc: @bogdan-sava |
planetf1
added a commit
to planetf1/egeria
that referenced
this issue
Aug 30, 2022
… noisy Signed-off-by: Nigel Jones <[email protected]>
planetf1
added a commit
to planetf1/egeria
that referenced
this issue
Aug 30, 2022
… noisy Signed-off-by: Nigel Jones <[email protected]>
planetf1
added a commit
that referenced
this issue
Aug 30, 2022
#6858 downgrade kafka in-loop debug info to DEBUG from INFO - too noisy
planetf1
added a commit
that referenced
this issue
Aug 30, 2022
#6858 downgrade kafka in-loop debug info to DEBUG from INFO - too noisy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Additional logging was added into this connector to aid in debugging some issues which occurred in a 'busy' k8s environment - relating to reliability & startup.
However some of these log entries are done at the DEBUG level, and occur during the processing of EACH message. This can make debugging of other areas more complex, and following a team discussions, we feel it would make more sense to demote these log entries to a lower level such as TRACE
Debug can still be used to help with understanding startup & error conditions & the flow in the code, but not for 'normal' message processing.
The text was updated successfully, but these errors were encountered: