Kyma

Appearance

Configure Application Logs ​

To collect logs that your applications write to stdout and stderr, create a LogPipeline. The application input is enabled by default and uses an agent on each node to tail container log files. You can control which namespaces and containers to include or exclude.

Prerequisites ​

  • You have the Telemetry module in your cluster.
  • You have access to Kyma dashboard. Alternatively, if you prefer CLI, you need kubectl.

Context ​

Use the application input section to restrict or specify which resources you want to include. You can define the namespaces to include in the input collection, exclude namespaces from the input collection, or choose that only system namespaces are included. For details, see LogPipeline: Custom Resource Parameters.

When you apply the LogPipeline resource to your Kubernetes cluster, a log agent is deployed and starts collecting the log data, transforms them to OTLP, and sends them to your backend. For details, see Transformation to OTLP Logs.

Enable or Disable Log Collection ​

The application input is enabled by default. To create a pipeline that only accepts logs pushed with OTLP, you can disable it.

yaml
  ...
  input:
    application:
      enabled: false     # Default is true

By default, input is collected from all namespaces, except the system namespaces kube-system, istio-system, kyma-system, which are excluded by default.

TIP

To select logs from specific namespaces and containers, or to include system namespaces, see Filter Logs.

Discard the Original Log Body ​

By default, the log agent preserves the original JSON log message by moving it to the attributes."log.original" field after parsing. For details, see Transformation to OTLP Logs.

To reduce data volume, you can disable this behavior. Set the parameter to false to discard the original JSON string after its contents are parsed into attributes.

yaml
  ...
    input:
      application:
        keepOriginalBody: false     # Default is true