Online reconfiguration basic effect display of Zorka monitoring platform

In the previous log, I briefly introduced the use of Zorka online reconfiguration, but did not describe how to see the effect of online changes, here is a brief talk.

As an example of the previous Tomcat, we will see TOMCAT.BSH in the directory Zorka\scripts\apache, which is the BeanShell file that tomcat corresponds to. Before we point to the listtracerincludes, we can see the following as shown:

When we open the Tomcat.bsh file, we can see that its 100 lines start with something like this:

if (Zorka.boolcfg ("tracer")) {  tracer.exclude ("    org.apache.naming.NamingContextBindingEnumeration")    , "org.apache.tomcat.jdbc.pool.**",    "org.apache.juli.logging.**"  );}

obviously, and the result in the interface above is one by one corresponding, if we comment out the middle line, then save, then click Reload, then click Listtracerincludes, you can see the previous content has become this:

As you can see, org.apache.tomcat.jdbc.pool.** does not have a line, and we use this method to verify that the online reconfiguration is actually implemented. A small question, what if the last line is commented out? We can find that does not work, the reason is also very simple: if you comment out the last line, the last line in parentheses more than a comma, should be broken BeanShell syntax rules, so Zorka choose not to parse this BSH file. Simply summarize so much.

If we want to learn Zorka's online reconfiguration function, where should we start? Should see Zorka How to respond to reload this mbean method, step by step upward, you can understand.

Online reconfiguration basic effect display of Zorka monitoring platform