Log module feature flags

New features are introduced to OneAgent log module and Dynatrace log module for Kubernetes.

Collect all container logs

OneAgent version 1.307+

If the option is disabled, then nothing changes. This is the default state for existing tenants to avoid introducing compatibility-breaking changes or altering ingest volume. Kubernetes logs are ingested and decorated the same way as before.

The option is enabled by default for new tenants, and when running Dynatrace Log module for Kubernetes. This enables improved capability for streaming logs from Kubernetes environments by:

Detection and collection of logs from short-lived containers and processes in Kubernetes
Detection and collection of logs from containers running processes not detected by OneAgent. For further reference, see Which are the most important processes?
Improved collection of logs from containers producing high volume of logs
Improved collection of logs from container wind-down
Log ingest configuration based on k8s.workload.name and k8s.workload.kind
Log ingest configuration based on pod annotations and labels
Log events decoration with k8s.workload.name and k8s.workload.kind

The matcher Deployment name in the log sources configuration will be ignored and needs to be replaced with Workload name. This requires Dynatrace Operator version 1.4.2+.

Enable Journald log detector

OneAgent version 1.307+

Enable OneAgent to collect logs from Journald on Linux systems. This option is enabled by default for new tenants, while existing tenants can opt-in. It still requires a proper ingest rule to be effective.