Log ingestion drop reasons

Latest Dynatrace
Reference
3-min read
Published Jun 05, 2026

Under certain conditions, logs sent to the ActiveGate API endpoint may be dropped before they reach Dynatrace.

Check your drop count

To see how many logs have been dropped and why, run the following DQL query:

timeseries drop_count = sum(dt.sfm.active_gate.event_ingest.drop_count),
  by:{drop_reason, dt.active_gate.id}

Drop reasons

The following table lists all possible drop reasons, their associated API response codes, and how to resolve them.

Drop reason	HTTP response code	Description
`timestamps_out_of_range`	400 – Bad Request	The log batch contains a log with a timestamp more than 24 hours in the past. Check and correct the timestamps in your payload.
`empty_messages`	400 – Bad Request	The log batch is empty. Make sure your payload contains at least one log record before sending.
`invalid_json_format`	400 – Bad Request	The log payload contains invalid JSON. Validate your JSON before sending.
`payload_byte_size_limit`	413 – Request Entity Too Large	A log in the batch exceeds the maximum allowed size. See Log ingestion limits for the request size limit.
`internal_buffer_size_limit_reached`	413 – Request Entity Too Large	A log in the batch exceeds the maximum allowed size. See Log ingestion limits for the request size limit.
`event_count_limit`	413 – Request Entity Too Large	The batch contains too many log records. See Log ingestion limits for the maximum number of log records per batch.
`tenant_throughput_limit`	429 – Too Many Requests	The tenant's log events per minute limit has been exceeded. See Log ingestion limits for details. This limit applies to Log Monitoring Classic only.
`serialization_exception`	500 – Internal Server Error	An unexpected internal error occurred. If this persists, contact Dynatrace Support.
`storage_not_running`	500 – Internal Server Error	An unexpected internal error occurred. If this persists, contact Dynatrace Support.
`unexpected_exception`	500 – Internal Server Error	An unexpected internal error occurred. If this persists, contact Dynatrace Support.
`head_on_queue_limit`	503 – Service Unavailable	The internal memory buffer is full. Check your current ingest volume. If this persists, scale out your ActiveGate.
`disk_queue_limit`	503 – Service Unavailable	The internal disk buffer is full. Check your current ingest volume. If this persists, scale out your ActiveGate.

Drop reasons

The following table lists all possible drop reasons, their associated API response codes, and how to resolve them.

Drop reason	HTTP response code	Description
`timestamps_out_of_range`	400 – Bad Request	The log batch contains a log with a timestamp more than 24 hours in the past. Check and correct the timestamps in your payload.
`empty_messages`	400 – Bad Request	The log batch is empty. Make sure your payload contains at least one log record before sending.
`invalid_json_format`	400 – Bad Request	The log payload contains invalid JSON. Validate your JSON before sending.
`payload_byte_size_limit`	413 – Request Entity Too Large	A log in the batch exceeds the maximum allowed size. See Log ingestion limits for the request size limit.
`internal_buffer_size_limit_reached`	413 – Request Entity Too Large	A log in the batch exceeds the maximum allowed size. See Log ingestion limits for the request size limit.
`event_count_limit`	413 – Request Entity Too Large	The batch contains too many log records. See Log ingestion limits for the maximum number of log records per batch.
`tenant_throughput_limit`	429 – Too Many Requests	The tenant's log events per minute limit has been exceeded. See Log ingestion limits for details. This limit applies to Log Monitoring Classic only.
`serialization_exception`	500 – Internal Server Error	An unexpected internal error occurred. If this persists, contact Dynatrace Support.
`storage_not_running`	500 – Internal Server Error	An unexpected internal error occurred. If this persists, contact Dynatrace Support.
`unexpected_exception`	500 – Internal Server Error	An unexpected internal error occurred. If this persists, contact Dynatrace Support.
`head_on_queue_limit`	503 – Service Unavailable	The internal memory buffer is full. Check your current ingest volume. If this persists, scale out your ActiveGate.
`disk_queue_limit`	503 – Service Unavailable	The internal disk buffer is full. Check your current ingest volume. If this persists, scale out your ActiveGate.