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
Articles about how to solve the most common problems
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Community Home
- Platform
- Troubleshooting
- Logs Troubleshooting Map
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Printer Friendly Page
noel_david
Dynatrace Helper
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
29 Jul 2026 07:21 AM - edited 29 Jul 2026 01:40 PM
- Logs Troubleshooting Map
- How to use this map
- Step 1 — Are logs visible in Dynatrace?
- Step 2 — Which ingestion method is used?
- Step 3 — Are logs visible but parsed incorrectly?
- Step 4 — Are log-based metrics or events silent?
- Step 5 — Are logs and traces not correlated?
- Step 6 — Are you seeing Dynatrace Managed cluster warnings?
Logs Troubleshooting Map
A decision-tree guide for troubleshooting log ingestion, parsing, processing, correlation, and alerting issues in Dynatrace.
Logs can be collected through OneAgent, OpenPipeline, Fluent Bit, FluentD, Syslog, ActiveGate Extensions, REST API ingestion, Kubernetes, Azure, Google Cloud, and more.
Use this map to quickly identify where the problem lies and jump directly to the most relevant troubleshooting article.
How to use this map
Work through the steps in order. The first one that matches your symptom is almost always the right entry point.
- Step 1 — Are logs visible in Dynatrace at all?
- Step 2 — Which ingestion method is used?
- Step 3 — Logs arrive, but do they look wrong?
- Step 4 — Are log-based metrics or events silent?
- Step 5 — Are logs and traces failing to correlate?
- Step 6 — Any Dynatrace Managed cluster warnings?
Step 1 — Are logs visible in Dynatrace?
If no, you are in the missing-logs category.
Typical symptoms
- No records returned in the Log Viewer
- Log monitoring is enabled but nothing appears
- Logs disappeared after a configuration change
- ActiveGate extension logs are missing
Troubleshooting articles
- Enable Log Visibility in Dynatrace — Start here if you're not sure log ingest was ever turned on for your environment or host group.
- Why are logs still missing after enabling Log Monitoring? —Log monitoring is on, host is monitored, but nothing shows up in Grail.
- Troubleshooting Missing Log Files Due to OneAgent Log Monitoring Security Rules - OneAgent Log Monitoring security rules might prevent a file from being collected.
- Logs Not Arriving from ActiveGate Extensions — Log Persistence Full — The extension reports OK but no logs surface; the persistence buffer is full.
- Troubleshooting Missing Logs in Log Module — You're on the new Grail Log module and specific sources drop out.
- What might prevent logs from appearing on the server? — Server-side prerequisites and permissions for Classic Log Monitoring.
If logs are visible, skip to Step 3.
Step 2 — Which ingestion method is used?
Pick the section that matches how logs enter Dynatrace.
REST API
Symptoms
POST /api/v2/logs/ingestfails or returns errors- Data accepted but never indexed
- Token or permission issues
- Payload rejected as malformed
Troubleshooting Log Ingestion via API
Fluent Bit
Symptoms
- Fluent Bit reports successful delivery, logs never reach Dynatrace
- OTLP conversion issues
- Records visible in Fluent Bit stdout but missing in Dynatrace
Troubleshooting Logs Ingested via Fluent Bit
FluentD
Symptoms
- Forwarder is working but only some logs land
- Partial ingestion, parsing failures
- Mixed-language or multi-byte payloads dropping fields
Multi-Language Log Ingest for Dynatrace via FluentD
Kubernetes / OpenShift
Symptoms
- Container logs missing for specific pods or namespaces
- Node-level agent collecting but nothing indexed
- OpenPipeline stage filtering out records unexpectedly
Articles
- Logs Ingest on Kubernetes with Dynatrace — End-to-end path check for K8s log ingest.
- Troubleshooting Kubernetes Logs in Log Module —Pipeline stages, sidecar assumptions, container discovery.
Azure
Symptoms
- Azure resource logs missing in Grail or Classic
- Azure Native Dynatrace integration reporting healthy, but no data
- Multi-tenant Azure subscriptions
Articles
- Azure Log Forwarder Troubleshooting — For the Function-App-based forwarder deployment.
- Fixing Missing Azure Resource Logs — Azure Native Integration — For the native integration (no forwarder).
- How can I get logs from an Azure subscription in another tenant? — Cross-tenant subscription setup.
Google Cloud
Symptoms
- Cloud Logging exports set up but Dynatrace shows no data
- GCP Monitor integration errors
Google Cloud Monitor Troubleshooting —
Syslog
Symptoms
- ActiveGate syslog receiver not ingesting
- RFC-5424 formatting issues
- Vendor-specific syslog payloads (firewalls, network gear) not parsing
Articles
- Syslog Ingestion Troubleshooting — General checklist: port, source, ActiveGate config.
- Syslog Ingestion via ActiveGate Troubleshooting Guide — Deeper dive on the ActiveGate-side receiver.
- Troubleshooting Syslog Ingestion When Standards Aren't Strictly Followed —Vendors that bend RFC-5424.
Rate limiting (HTTP 429)
Symptoms
- Ingest endpoint returns HTTP 429
- Some records land, others silently drop
Dynatrace does not ingest logs (HTTP 429)
Ingest delay (any source)
Symptoms
- Logs eventually appear, but minutes late
- Delay grows during traffic spikes
Troubleshooting Log Ingest Delay in Log Module
Step 3 — Are logs visible but parsed incorrectly?
JSON parsing issues
Symptoms
- JSON fields appear collapsed inside the
contentfield - Expected attributes are not extracted
Troubleshooting JSON Parsing in Log Module
Log boundary detection issues
Symptoms
- Stack traces split across multiple entries
- Multi-line events broken up
Troubleshooting Log Boundary Detection in Log Module
Log rotation issues
Symptoms
- Gaps in ingestion aligned with log rotation times
- Rotated files re-read, causing duplicates
- New file not picked up
Troubleshooting Log Rotation Issues in Log Module
Ingested logs don't look as expected
Symptoms
- Content is truncated, reordered, or missing fields
- Attributes are dropped or renamed
Why don't ingested logs look as expected?
Attribute key mismatch
Symptoms
- Warning banner in Log Viewer about mismatched attribute keys
Articles
- Ingest warning about an attribute key case mismatch — What the warning means and how to fix it at the source.
- How to enable the attribute key mismatch feature — For Managed operators who need to turn the check on.
Case-sensitive query issues
Symptoms
- Queries return unexpected results
- Search only works with exact capitalization
Articles
Timestamp issues
Symptoms
- Log entries appear out of order
- Timestamp drift after an agent upgrade
- Behavior changed after moving to OneAgent 1.313+
Timestamps in Logs with OneAgent 1.313+
Log enrichment overhead
Symptoms
- CPU or memory spikes on hosts running the log enrichment component
- Performance regression after enabling log enrichment features
High Resource Overhead from the Log Enrichment Component
Step 4 — Are log-based metrics or events silent?
Symptoms
- A log-based metric exists but shows no data
- Log-based event never triggers
- Problem opens against the wrong entity
Articles
- Dynatrace Log Monitoring — Metric Shows No Data — Metric definition exists, timeseries is empty.
- How to Change Impacted Entity for a Log-Based Event or Problem — Event fires but attaches to the wrong host/service/process.
Step 5 — Are logs and traces not correlated?
Symptoms
- "View Trace" option missing on a log entry
- Trace ID is present in the log payload but no link is drawn
- Logs-to-Traces navigation unavailable
Why I Can't See Traces in Log View Page
Step 6 — Are you seeing Dynatrace Managed cluster warnings?
Log ingest queue full
Symptom: cluster warning "Log ingest queue is full".
Log Ingest Queue Is Full — Dynatrace Managed
Log data trimmed
Symptom: cluster warning "Ingested log data is trimmed".
Labels:
