split snmp-graph.properties
Description
Environment
Acceptance / Success Criteria
Attachments
blocks
is duplicated by
Lucidchart Diagrams
Activity

Ronny Trommer November 26, 2012 at 8:18 PM
Single commit in master with b7d0e084865fbeff805b8d928f5556ad270e7ff5
Tried to split as defensive as possible. Put reports=... entry in a single line to have the possibility to have a sanity check against report definitions.

Seth Leger September 19, 2011 at 12:05 PM
Deferring to 1.11, it is too late to put configuration file changes like this into the 1.10 release candidates.

Alejandro Galue September 16, 2011 at 8:27 AM
I'm completely agree with Matt on this.

Matt Brozowski September 12, 2011 at 2:49 PM
Sorry... I meant we should break this issue up into different bugs for different files we would like to break up.

Alejandro Galue September 12, 2011 at 2:10 PM
I did the work for datacollection-config.xml and Craig did the work for snmp-graph.properties
My work does not apply for jmx-datacollection-config.xml, http-datacollection-config.xml, nsclient-datacollection-config.xml, wmi-datacollection-config.xml, xmp-dtacollection-config.xml and jdbc-datacollection-config.xml
Craig's work (if I understood correctly) does not apply for response-graph.properties and/or *adhoc-graph.properties.
So, you could close it, and if someone require to apply something similar to the exceptions mentioned before, we could open new issues for them.
I suggest that some sort of "split" configuration be used to aid upgrades. By
this, I mean that some configuration files (snmp-graph.properties for example)
should check two locations - the "base" distributed file, and a second
"customised" file. Items in the second override the base file, if they
conflict. Otherwise the result is the union of those two files. This will not
work for all config files (the semantics aren't there), but for the ones it will
work on, it would significantly decrease the burden of upgrading. New
distributed files can be dropped into place over the old, and any customisations
will still exist without having to manually merge them together.