-
Notifications
You must be signed in to change notification settings - Fork 867
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
Logging agent logs separately #7179
Comments
Hello! Can I get any response please! |
You should be able to redirect agent logs to file with |
Thanks for the info. But as I see, agent uses a simple logger, and does not have rolling policy. Some times, in case otel collector goes down, logs would pile up in single application file. Are there any plans to make changes to simple logger? Would like to know and contribute if there are any such plans. Thanks! |
Hey folks! Is it possible to, when working with logback in spring, specify somehow via property |
Hey @michaeltcoelho , |
It works perfect if specified as JVM argument. Is it possible to specify this property in an javaagent configuration file? UPD: Looks like only system properties is the way to configure at the moment |
Nope - the reason for that is that logging is initialized as one of the first javaagent subsystems, way before full configuration is assembled. |
Hi @mateuszrzeszutek , |
Hey @lgext06 , |
|
Currently opentelemetry agent logs in the application logs itself. This pollutes the application logs, and also if there are any errors, they spam the application logs.
Currently agent uses slf4j simple to log these logs.
Can the logs be moved to a log file? It would be a cleaner approach. I would like to know if above approach was done due to some issues faced.
I'm thinking if we can add slf4j-api with logback. Let me know what can be the complications involved if I do so.
The text was updated successfully, but these errors were encountered: