You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can think of 2 ways that multiple XML files can be specified:
on the arguments passed into the agent -javaagent:jmxetric-1.0.4.jar=$args
where args=config=etc/jmxetric.xml:etc/anotherFile.xml
as a node in the XML file, maybe like how a <link> tag works in HTML. It could look like this <link src="etc/anotherFile.xml">, and anotherFile.xml will be parsed for samples.
2 seems to be a good option, but how do we resolve the issue that 2 XML files specify different <ganglia> configuration? For example if the hostname is different. Or should it be restricted to only specifying samples?
The relevant code to do this is in JMXetricXmlConfigurationService.
For now, this implementation is based on an my unmerged PR #23, because it is easier to implement it on that.
Also, this implementation dictates that jmxetric.xml is the entry point of configuration, and other XML files are limited because they can only configure samples.
Currently, JMXetric is configured by jmxetric.xml
It would be useful if jmxetric.xml could source metrics from additional XML files and merge all the attribute definitions.
This would enable sharing config fragments between several JVMs on the same host.
The text was updated successfully, but these errors were encountered: