And if your apps are using an APM tool agent such as AppDynamics or
NewRelic, it's likely you'd be able to invoke the JMX mbean via the APM
tool GUI

On 12 Aug 2016, at 05:21, Mike Youngstrom <youngm(a)gmail.com> wrote:

That would depend on the log framework your application is using. I know
Jul has a jmx mbean exposed. Not sure about others. You may need to
modify your app to expose an mbean.

Mike

On Aug 11, 2016 3:40 PM, "Siva Balan" <mailsiva(a)gmail.com> wrote:

Thanks Mike. Assuming I have access to update using JMX, the question
still remains on what should I update to change logging level. I dont
believe they are exposed through JMX. Am I missing something?

On Thu, Aug 11, 2016 at 2:24 PM, Mike Youngstrom <youngm(a)gmail.com>
wrote:

Your app could expose an endpoint. Or you can enable JMX in the java
buildpack and ssh port forward to your running app and use a jmx console to
change some runtime config.

Mike

On Thu, Aug 11, 2016 at 12:52 PM, Siva Balan <mailsiva(a)gmail.com> wrote:

We have a wide variety of Java apps(mostly spring boot) deployed to CF.
One of the challenges we have is to troubleshoot issues in Production when
these apps are running with a log level of INFO or higher(ERROR, WARN and
FATAL). Is there a way to dynamically change the log level from INFO to
DEBUG or TRACE for apps running on CF without having to redeploy the app or
restage the app in Production?

Thanks,
Siva

--
http://www.twitter.com/sivabalans

--
http://www.twitter.com/sivabalans