Log Level
Ververica Platform lets you configure the log level for platform components through the Helm values.yaml file. You can set a global log level that applies to all components, and override it for individual components as needed.
Configuration
Global Log Level
Set global.logLevel to apply a log level to all platform components:
1global:
2 logLevel: INFOPer-Component Override
Set <component>.logLevel to override the global level for a specific component:
1global:
2 logLevel: INFO
3
4appManager:
5 logLevel: TRACEIn this example, AppManager runs at TRACE while all other components run at INFO.
Valid Log Levels
Levels are listed in ascending order of urgency. Setting a level captures all messages at that level and above. For example, WARN captures WARN and ERROR messages only.
The default log level is INFO. Each component's logback.xml configuration consumes the logLevel environment variable with a fallback of INFO, so omitting global.logLevel from values.yaml is equivalent to setting it to INFO.
Apply Changes
After editing values.yaml, apply the changes by running:
1helm upgrade --install <RELEASE_NAME> \
2 oci://registry.ververica.cloud/platform-charts/ververica-platform \
3 --version 3.1.1 \
4 --namespace <NAMESPACE> \
5 --values values.yamlComponents whose log level changed restart automatically during the upgrade.
Verify
To confirm the log level is in effect, inspect live logs for a component pod:
1kubectl logs -n <NAMESPACE> <POD_NAME> --tail=50At TRACE or DEBUG level, output includes significantly more entries than at INFO. At WARN or ERROR, only warning and error messages appear.