Foglight for JMX agent has been setup to monitor custom MBeans. The mbean object name has a property that dynamically changes every time the process restarts. This creates multiple topology objects and the number keeps growing over time. Is there a way to avoid this kind of scenario?
There is currently no workaround from Foglight at the moment. The Mbean's ObjectName should not have been designed as such to avoid this scenario in the first place.
Enhancement request number JMX-432 has been submitted to Development for consideration in a future release of Foglight for JMX Cartridge.