Hi Team,
Can some one help me who already enabled below attribute ([config_change_audit] in Version 8.2.4 or 8.2.7 . below caution was mentioned in document.
* CAUTION: This setting is experimental and is related to a feature that is still under development. Using the setting might increase resource usage.
What is the Experimental feature ?
What will risk to the environment a part from resource usage?
And if its enabled in environment what will be resource utilizations ?
================================================================================================================
[config_change_audit]
disabled = <boolean>
* Whether or not splunkd writes configuration changes to the
configuration change log at $SPLUNK_HOME/var/log/splunk/configuration_change.log.
* If set to "false", configuration changes are captured in
$SPLUNK_HOME/var/log/splunk/configuration_change.log.
* If set to "true", configuration changes are not captured
in $SPLUNK_HOME/var/log/splunk/configuration_change.log.
* Default: true
mode = [auto|track-only]
* Set to "auto" or "track-only" to get log of .conf file changes
under $SPLUNK_HOME/etc/system, $SPLUNK_HOME/etc/apps,
$SPLUNK_HOME/etc/users, $SPLUNK_HOME/etc/slave-apps or changes to $SPLUNK_HOME/etc/instance.cfg.
* The values "auto" and "track-only" are identical in their effects. Set mode to "auto"
to auto-enroll this deployment into all the latest features.
* CAUTION: This setting is experimental and is related to a feature that
is still under development. Using the setting might increase resource usage.
* Default: auto ==========================================================================================================
... View more