Reloading Application Configurations
Unified Assurance Services load any rule sets and application configuration on startup and when prompted by a Reload Config command. This means the service configuration and any rule sets can be updated and validated before the changes are implemented and without requiring a restart of the service. Once a reload is initiated, the new application configuration settings are validated and any rule sets are re-read, syntax checked, and validated before being used. If a new configuration setting or rule set does not pass validation, the application reverts to the last known good setting for the configuration and logs the issue before continuing.
Usage
A reload can be initiated on a service either through the UI or from the command-line Broker Control.
UI
-
Navigate to the Services UI.
-
Select the service to update configuration.
-
Update configuration as needed (e.g. Change LogLevel to DEBUG) and save.
-
Select the service again, then click on Reload Config in the button bar.
-
If the service LogLevel is set to INFO or DEBUG, verify application reloaded by reviewing the logs for an INFO line containing Configuration Reloaded in [xxx].
Note:
This can take up to a poll cycle in metric services.
Broker Control
-
Navigate to the Services UI.
-
Select the service to update configuration, make note of the value in the ID column.
-
Update configuration as needed (e.g. Change LogLevel to DEBUG) and save.
-
Open a console to the Unified Assurance server the service is on and navigate to $A1BASEDIR.
-
Run the following command replacing
with the correct value from step 2: ./bin/BrokerControl -b reloadappconfig <SERVICEID> -
If the service LogLevel is set to INFO or DEBUG, verify application reloaded by reviewing the logs for an INFO line containing Configuration Reloaded in [xxx].
Note:
This can take up to a poll cycle in metric services.
Best Practices
-
Reload of configuration may not be immediate. Depending on the app, it can take up to the next poll time before the reload is processed.
-
Not all application configurations can be reloaded while the service is running (e.g. Host and Port usually cannot be changed). Refer to the individual application's documentation for supported reloadable configurations.
-
Changes to the CheckTime configuration are recognized after the next ConfigCheck cycle e.g. if CheckTime is 15 minutes and the new value will be 5 minutes, the application will run the normal 15 minute ConfigCheck cycle before then checking every 5 minutes.