This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Troubleshooting missing logs
Summary
This article helps you troubleshoot situations where logs you expect to be ingested by Log Module are missing from Dynatrace. It a...
...Logs will not appear in Dynatrace even though the monitored sources appear healthy.
When can this problem be observed?
This problem typically surfaces in the following situations:
High l...
Logs Troubleshooting Map
A decision-tree guide for troubleshooting log ingestion, source health, delays, volume, parsing, correlation, and alerting issues in Dynatrace.
First time h...
Table of contents
Summary
This article helps you troubleshoot Kubernetes-specific log collection issues with Log module. It covers no logs appearing, missing or incorrect Kubernetes m...
Summary
In April 2025, Dynatrace released a log module feature for automatic log ingest of container logs on clusters monitored with OneAgent workload in Cloud Native Fullstack or App-only modes o...
...neAgent or Dynatrace Operator on both SaaS and Managed environments, and covers file-based logs and container stdout/stderr logs on Linux and Windows, including Kubernetes workloads.
Problem
You see one o...
...log entry uses a custom JSON field for its timestamp, but Log module doesn't pick it up.
Severity (log level) values in ingested logs don't match the values written by the application, for e...
Table of contents
Summary
This article helps you troubleshoot situations where logs are ingested into Dynatrace later than expected when using Log module (deployed via OneAgent or D...
Log monitoring is turned on by default, but this setting might have been changed.
Ensure that OneAgent log ingestion is turned on in your Dynatrace environment: Go to Setting...
