Configuration relies on commons-monitoring.properties file which should be found in the commons-monitoring-core classloader.
Note: you can change the file name using org.apache.commons.monitoring.configuration system property.
org.apache.commons.monitoring.configuration.Configuration has several utility methods to get int, boolean… from the properties file. You can reuse it in your monitoring extensions if you want.
Another interesting usage of Configuration class is to be a basic lifecycle handling of your objects. Using org.apache.commons.monitoring.configuration.Configuration.newInstance method you can decorate your class methods with org.apache.commons.monitoring.configuration.Configuration.Created and org.apache.commons.monitoring.configuration.Configuration.Destroying to get lifecycle hooks.
Destroying is called when the monitoring is stopped. Generally since commons-monitoring-core is deployed in the container or JVM classloader it is with the JVM but sometimes you can deploy it in your application. In this case you’ll need to either configure the javax.servlet.ServletContextListener org.apache.commons.monitoring.web.lifecycle.CommonsMonitoringLifecycle from reporting module or to call manually Configuration.shutdown() method.