Logging

This page describes how to configure logging for a SchemaRegistryBackup.

Default behaviour

By default, the operator propagates the global logging settings (global.logging.format and global.logging.level) to every SchemaRegistryBackup pod it creates. See Logging configuration for details.

Overriding the log level

You can override the log level for a specific SchemaRegistryBackup by setting the KANNIKA_LOG_LEVEL environment variable in the SchemaRegistryBackup specification.

apiVersion: io.kannika/v1alpha
kind: SchemaRegistryBackup
metadata:
  name: backup
spec:
  source: "my-registry"
  sink: "my-storage"
  extraEnvVars:
    - name: KANNIKA_LOG_LEVEL
      value: "debug"

The available logging levels are:

• error: Logs only error messages.
• warn: Logs warning and error messages.
• info: Logs informational messages, warnings, and errors.
• debug: Logs detailed debugging information, informational messages, warnings, and errors.
• trace: Logs very detailed tracing information, debugging information, informational messages, warnings, and errors.

Overriding the log format

You can also override the log format for a specific SchemaRegistryBackup by setting the KANNIKA_LOG_FORMAT environment variable.

apiVersion: io.kannika/v1alpha
kind: SchemaRegistryBackup
metadata:
  name: backup
spec:
  source: "my-registry"
  sink: "my-storage"
  extraEnvVars:
    - name: KANNIKA_LOG_FORMAT
      value: "text"

Advanced: RUST_LOG

For fine-grained control, you can set the RUST_LOG environment variable. When RUST_LOG is set, it takes full precedence over KANNIKA_LOG_LEVEL.

apiVersion: io.kannika/v1alpha
kind: SchemaRegistryBackup
metadata:
  name: backup
spec:
  source: "my-registry"
  sink: "my-storage"
  extraEnvVars:
    - name: RUST_LOG
      value: "info,kannika=trace"