Configuring server logging

It is possible to fine-tune the log levels of individual loggers available in the Che server.

The log level of the whole Che server is configured globally using the cheLogLevel configuration property of the Operator. See CheCluster Custom Resource fields reference. To set the global log level in installations not managed by the Operator, specify the CHE_LOG_LEVEL environment variable in the che ConfigMap.

It is possible to configure the log levels of the individual loggers in the Che server using the CHE_LOGGER_CONFIG environment variable.

Configuring log levels

The format of the value of the CHE_LOGGER_CONFIG property is a list of comma-separated key-value pairs, where keys are the names of the loggers as seen in the Che server log output and values are the required log levels.

In Operator-based deployments, the CHE_LOGGER_CONFIG variable is specified under the customCheProperties of the custom resource.

For example, the following snippet would make the WorkspaceManager produce the DEBUG log messages.

...
server:
  customCheProperties:
    CHE_LOGGER_CONFIG: "org.eclipse.che.api.workspace.server.WorkspaceManager=DEBUG"

Logger naming

The names of the loggers follow the class names of the internal server classes that use those loggers.

Logging HTTP traffic

It is possible to log the HTTP traffic between the Che server and the API server of the Kubernetes or OpenShift cluster. To do that, one has to set the che.infra.request-logging logger to the TRACE level.

...
server:
  customCheProperties:
    CHE_LOGGER_CONFIG: "che.infra.request-logging=TRACE"