Display the basic Online reconfiguration results of the Zorka Monitoring Platform

Display the basic Online reconfiguration results of the Zorka Monitoring Platform

In the previous article (), I briefly introduced how to use the Online reconfiguration of Zorka, but I didn't explain how to see the Online changes.

Take tomcat as an example. We can see tomcat. bsh in the directory zorka \ scripts \ apache, that is, the beanshell file corresponding to tomcat. When we click listTracerIncludes, we can see the following:

When we open the tomcat. bsh file, we can see that its row 100 starts with the following content:

If (zorka. boolCfg ("tracer ")){
Tracer. exclude (
"Org. apache. naming. NamingContextBindingEnumeration ",
"Org. apache. tomcat. jdbc. pool .**",
"Org. apache. juli. logging .**"
);
}

Obviously, it corresponds to the results in the above interface. If we comment out the middle line, save it, Click reload, and then click listTracerIncludes, the previous content becomes as follows:

We can see that the org. apache. tomcat. jdbc. pool. ** line does not exist. We use this method to verify that Online reconfiguration can be implemented. A small problem. What if I comment out the last line? We can find that it does not work, but the reason is actually very simple: if you comment out the last line and add a comma to the last line in the brackets, the Beanshell syntax rules should be broken, therefore, Zorka chooses not to parse this bsh file. So much.

If we want to learn about Zorka's Online reconfiguration function, where should we start? Let's take a look at how Zorka responds to the Reload MBean method and push it up step by step.

This article permanently updates the link address: