This demo is a sample app to build the collector and exercise its kubernetes logs scrapping functionality.

Switch to this directory and run following command: kubectl apply -n <namespace> -f otel-collector.yaml

Kubernetes logs are being stored in /var/log/pods. Path to container logs is constructed using following pattern:

/var/log/pods/<namespace>_<pod_name>_<pod_uid>/<container>/<restart_count>.log

You can use it to manage from which containers do you want to include and exclude logs.

For example, to include all logs from default namespace, you can use following configuration:

include:
    - /var/log/pods/default_*/*/*.log
exclude: []

Two steps are required to build and run the demo:

1. Build latest docker image in main repository directory make docker-otelcontribcol
2. Switch to this directory and run docker-compose up

varlogpods contains example log files placed in kubernetes-like directory structure. Each of the directory has different formatted logs in one of three formats (either CRI-O, CRI-Containerd or Docker). This directory is mounted to standard location (/var/log/pods).

otel-collector-config is a configuration to autodetect and parse logs for all of three mentioned formats

There are multiple tests for various configurations in testbed. Following table shows result of example run:

To cover kubernetes system logs, logs from journald should be supported as well.