Log Configuration
Log configuration updates the log levels, maximum size of the log files, and log rotation parameters on the appliance and/or connector. If the configuration update is triggered on the appliance, appliance controller log settings are updated. On the other hand, if the configuration update is triggered on a connector, service controller and service log settings are updated.
|
Parameter Name |
Type |
Description |
|---|---|---|
|
Logging level |
dropdown |
Logging level to be set |
|
Debug log level |
|
|
Informational log level |
|
|
Warning log level |
|
|
Error log level |
|
|
Max log file size (in MB) |
number |
Maximum size of a log file before log rotation kicks in |
|
Log rotation (in days) |
number |
Maximum age of a log file before log rotation kicks in |
|
Log rotation (in instances) |
number |
Maximum instances of log files kept |
Test: No op.
Apply: If the configuration is trigged on an appliance, update the configuration file of tet-controller on the appliance. If the configuration is triggered on a connector, update the configuration files of tet-controller and the service managed by the controller on the Docker container responsible for the connector.
Allowed Secure Workload virtual appliances: All
Allowed connectors: NetFlow, NetScaler, F5, AnyConnect, ISE, ASA, and Meraki.
|
Since all alert notifier Connectors (Syslog, Email, Slack, PagerDuty, and Kinesis) run on a single Docker service (Secure Workload Alert Notifier) on Secure Workload Edge, it is not possible to update the log config of a connector without impacting the config of another alert notifier connector. The log configurations of Secure Workload Alert Notifier (TAN) Docker service on Secure Workload Edge appliance can be updated using an allowed command. |
See Update Alert Notifier Connector Log Configuration for more details.