-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
JMX agent interfering with logging format of application #976
Comments
@mapsacosta The exporter doesn't set any system properties. The exporter Logger is a wrapper around I suspect what is happening is that the exporter Logger code is initializing the Because...
... is executed in application code, after the initial calls to Can you test passing passing the format as JVM argument? i.e. |
Just encountered the same issue.
|
We set the logger format through JAVA_OPTS as you all suggested and it fixed the problem for us. Thank you! |
We have started monitoring our application with the JMX exporter. Everything works well in terms of metrics, but we are experiencing a strange side effect. Our application log format gets overridden and we get a different logging format that messes with some of our other monitoring.
Our application has a specific logging format
which translates to:
However, when we start the application with JMX exporter java agent, our logs become unreadable. The same startup log lines look like:
Has anyone else encountered this? Is there a way to override jmx exporter logging format to fit our original log structure? Why is the exporter overriding application-specific settings?
Thanks
The text was updated successfully, but these errors were encountered: