We generally have standard configurations (created via superpacks) that are applied to say a Linux fleet. However we do have some adhoc changes requested from clients that deviate from the standard configuration.
There is a possibility of this configuration being lost when the cdm configuration is removed and standard configuration applied as we are not aware of the changes made.
We have difficulty keeping track of these changes and would like to know the recommended or suggested solution to keep track of these changes. Kindly advise. TQ
Hello Ragupathy, please have a look at the opportunities you have for configuring probes and manage configuration changes in the Monitoring Configuration Service.
Similarly, the cfx file is not a configuration file, it is a list of instructions on how to change existing cfg file.
Each <section> takes a modification directive (blank, "edit", "clear", "delete", "overwrite") that applies to the following sections.
So if you have a threshold that you don't want changed instead of the typical
You would use
because no directive specified means "add if not there otherwise leave alone".
And because the cfx file isn't a cfg file, there's no limit on the number of times a section can occur.
It does get trickier on the probes that automatically configure themselves - like allowing cdm to auto detect filesystems but that's not impossible to achieve.
One alternative is to script the process of applying the customizations - or scripting the cfg deployment instead of using packages.