-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reloading jmxetric XML configuration at runtime #19
Comments
I just learned that MBeans can provide attributes and operations. Can JMXetric provide an MBean for its process, and have an operation that will cause a reload of the configuration file? |
That is exactly what I had in mind. This is not the most urgent task to complete, but it will be very useful. There are many tutorials online about how to make an MBean like this - that part is probably easy. The more difficult task will be working out how to cleanly reconfigure or destroy and recreate all the GMetric objects in JMXetric. |
Perhaps in addition to a jmx operation to force a reload, we could include a configuration refresh interval in the xml config, that would cause jmxetric to reload its configuration on that interval. I would consider such an option very useful for monitoring production applications that can't easily be restarted just to add more metrics. |
Currently, the JVM must be restarted to detect any changes in the JMXetric config file.
It should be able to reload the file at runtime, possibly be detecting changes to the file or reloading when there is a signal or a command from JMX / JConsole.
The text was updated successfully, but these errors were encountered: