Configuration changes between 1.22 and 1.24
Confd configuration changes
Below are the changes to the confd configuration between versions 1.22 and 1.24 listed.
Added services.routing.settings.qoeTracking.requestsIgnoredAfterHostChange
The services.routing.settings.qoeTracking.requestsIgnoredAfterHostChange
setting configures the number of requests to ignore for QoE tracking after a
host change.
Removed unused tuning items
The following tuning items were not used and have been removed:
services.routing.tuning.general.cpuLoadWindowSizeservices.routing.tuning.general.repeatedSessionStartThresholdSecondsservices.routing.tuning.general.selectionInputMetricsTimeoutSeconds
Made items in services.routing required
The items under services.routing were previously marked as optional, but are
now required. A configuration that missed some of these items would previously
have been valid, but starting with 1.24 it will be invalid.
The items that are now required are:
services.routing.accountsservices.routing.applyConfigservices.routing.classifiersservices.routing.dataStreamsservices.routing.entrypointservices.routing.hostGroupsservices.routing.rulesservices.routing.sessionGroupsservices.routing.settingsservices.routing.translationFunctionsservices.routing.tuning
Added services.routing.tuning.general.responseCodeTracking
The services.routing.tuning.general.responseCodeTracking setting enables
tracking of the last response code received from each CDN host. If all CDNs
return errors, the Director will respond with the last received error code
instead of a generic 403.
Moved all logging configuration to services.routing.settings.logging
All logging configuration has been moved to
services.routing.settings.logging. The section contains log level, access log
and usage log configuration.
The following items have been added to the logging configuration:
accessErrorLogandaccessErrorLogDepth- see Access Error Log.moduleLogLevels- enables fine-grained log levels per module.