Docs Home
Viewing docs for
Self-ManagedNot available for BYOC

Log Level

On this page

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:

YAML
1global:
2  logLevel: INFO

Per-Component Override

Set <component>.logLevel to override the global level for a specific component:

YAML
1global:
2  logLevel: INFO
3
4appManager:
5  logLevel: TRACE

In this example, AppManager runs at TRACE while all other components run at INFO.

Valid Log Levels

LevelDescription
TRACEMost detailed. Includes all lower-priority messages.
DEBUGDetailed diagnostic information.
INFOInformational messages about normal operation. Default.
WARNPotential issues that do not stop the component.
ERRORError conditions and exceptions.

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.

Apply Changes

After editing values.yaml, apply the changes by running:

BASH
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.yaml

Components 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:

BASH
1kubectl logs -n <NAMESPACE> <POD_NAME> --tail=50

At TRACE or DEBUG level, output includes significantly more entries than at INFO. At WARN or ERROR, only warning and error messages appear.

Was this helpful?