Troubleshooting Log Monitoring (Logs Classic)

How much does Log Monitoring cost?

Log Monitoring pricing is based on the Davis data units (DDUs) model. See DDUs for Log Monitoring Classic for details on how DDU consumption is calculated for Log Monitoring.

Who can increase the ingestion limit per tenant?

Contact a Dynatrace product expert via live chat within your Dynatrace environment.

I get an ingest warning about an attribute key case mismatch.

In the ingested logs pipeline, an attribute key is detected that matches either the custom attribute key or the semantic attribute key, but there's a case mismatch in the attribute key. To view details about mismatched attribute keys, enable log ingest debug information in the Debug Settings.

I get a warning in the Log Viewer about case-sensitive queries.

Pay attention to the letter case of attribute names in your query. Soon log queries will be case-sensitive, meaning that to find your logs you need to write the attribute names in your query with the same letter case as they were when they were ingested.

Ingested logs don't look as expected.

I don't see my logs, or log events are missing in Dynatrace Managed.

I get Ingested log data is trimmed. message in Dynatrace Managed.

I get Log ingest queue is full. message in Dynatrace Managed.

I get Elasticsearch log queue is full. message in Dynatrace Managed.

What might prevent logs from appearing on the server?

I want to enable the attribute key mismatch feature.

I get a warning in the Log Viewer about case-sensitive queries.

I get an ingest warning about an attribute key case mismatch.

I get a warning in the Log Viewer about case-sensitive queries.