Agent or client app restart needed when changing agent log level?

[Anonymous]

I am not putting this question in any of the specific agent forums because I am asking a general question.

Do we need to restart a client app or JVM or .net coordinator service, or our DB agent... when changing the agent log levels? I cannot find a clear answer in the docs.

I am assuming we don't have to do any of this because we can request agent log files with a certain log level from the GUI - without restarts or anything. But I would like someone to confirm, please. I don't have a lab environment to test this by myself, that's why.

[Ryan.Paredez]

Hi @Anonymous,

Were there any specific Docs you found that touched on this subject but it was not clear or were you not able to find anything about that topic at all?

[Anonymous]

Yes, I've looked into these pages:

https://docs.appdynamics.com/display/PRO21/Agent+Log+Files

https://docs.appdynamics.com/display/PRO21/Java+Agent+Logging

https://docs.appdynamics.com/display/PRO21/.NET+Agent+on+Windows+Logging

https://docs.appdynamics.com/display/PRO21/Database+Agent+Logging

Maybe this means that the restart is not needed - since the docs are not mentioning that at all, but it would be useful if we would know for sure. I think the docs should mention it since there are many knobs and tweaks in the agents that require restart (of the agent itself or the application).

[Ryan.Paredez]

Hi @Anonymous,

Thank you for sharing those links. I have created a ticket for their team to look into it. I, unfortunately, don't know the answer to your question though. Let's see if the Community can jump in in the meantime. I will be sure to update the thread when I hear back from the Docs team though.

[Ryan.Paredez · Accepted solution]

Hi @Anonymous,

Agent restart is not needed!