-
Notifications
You must be signed in to change notification settings - Fork 961
Excessive Kafka client logging in WebSphere Application Server with OpenTelemetry Java Agent #13833
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
Comments
Looks like you are creating and closing a lot of |
@laurit Thank you for the quick feedback! I appreciate your suggestions. I can confirm that this excessive logging only occurs only when the OpenTelemetry Java Agent is enabled. Without the agent, our application logs are normal. I'll try disabling the Regarding setting a breakpoint in AbstractConfig.java - I'm not sure how to approach this in our environment since we are using packaged Pega application and I am not sure we have access to the related source code to set breakpoint. Is there an alternative approach you could suggest to help diagnose what's triggering these logs? I'll report back after testing with the Thanks again for your help! |
I suggested setting breakpoint in kafka client code which is open source and readily available. Source might not even be needed, for example in intellij you can set method breakpoints just by knowing class and method name. |
This has been automatically marked as stale because it has been marked as needing author feedback and has not had any activity for 7 days. It will be closed automatically if there is no response from the author within 7 additional days from this comment. |
Description
After instrumenting our application running on WebSphere Application Server with the OpenTelemetry Java Agent, we're experiencing excessive logging related to Kafka clients. These logs are generated continuously (multiple times per second), quickly filling up disk space and overwhelming other important log information in the SystemOut.log file.
The logs appear to be coming from the Kafka client instrumentation, showing repeated consumer creation, configuration, and closing cycles. This is causing:
Environment
Log Sample
The text was updated successfully, but these errors were encountered: