From Genesys Documentation
This topic is part of the manual Designer Private Edition Guide for version Current of Designer.
Learn how to configure log levels for Designer and DAS.
Designer and DAS support console output (stdout) logging. Genesys recommends configuring console output logging to minimize the host IOPs and PVCs consumption by using log volumes. Console output logs can be extracted using log collectors like fluentbit/fluentd and Elasticsearch.
Ensure the below setttings are configured in the respective values.yaml overrides for console logging:
designerEnv.envs.DES_FILE_LOGGING_ENABLED = false
dasEnv.envs.DAS_FILE_LOGGING_ENABLED = false
dasEnv.envs.DAS_STDOUT_LOGGING_ENABLE = true
Post deployment, Designer and DAS log levels can be modified as follows:
- Configure the
loggingsetting in the flowsettings override (flowsettings.yaml) - Refer to the table in the Post deployment Designer configuration settings section for option descriptions.
- Execute the steps in the Updating the flowsettings file section in Post deployment procedures for the changes to take effect .
- Configure the
dasEnv.envs.DAS_LOG_LEVELsetting in the Helm das-values.yaml file. For setting descriptions, refer to the DAS deployment settings section in Deployment configuration settings.
- Execute the steps in the Upgrade section in the DAS deployment process for the Blue-Green strategy. The same DAS version running in production can be used for the upgrade,
- Execute the steps in the Cutover section in the DAS deployment process for the Blue-Green strategy.
Comments or questions about this documentation? Contact us for support!