Expected behavior

All logs available using

traces
| where cloud_RoleName == "app"
| order by timestamp desc

Actual behavior

Some log records missing:
1/4/2022, 12:33:02.355 PM ...
[missing]
1/4/2022, 12:32:28.396 PM ...

Happens regularly during Camel routes activated by scheduler (import from file to in-memory SQL DB):

Route 1 started at 01:30: 1/6/2022, 1:30:31.790 AM | * Queue is full (5894 times)

Route 2 started at 05:00: 1/6/2022, 5:05:31.796 AM | * Queue is full (2456 times)

System information

• SDK Version: 3.2.4 (no such issue with 3.1.1)
• OS type and version: Linux 5.4.0-1062-azure x86_64
• Application Server type and version (if applicable): Tomcat 8.5.58
• Using spring-boot? No
• Additional relevant libraries (with version, if applicable): AKS 1.20.13, no CPU limit set,
  IngestionEndpoint=https://northeurope-0.in.applicationinsights.azure.com/
  Camel 2.20.1, instrumentation is not configured
  OpenJDK Runtime Environment (Zulu 8.42.0.23-linux64)-Microsoft-Azure-restricted (build 1.8.0_232-b18)
  OpenJDK 64-Bit Server VM (Zulu 8.42.0.23-linux64)-Microsoft-Azure-restricted (build 25.232-b18, mixed mode)

Logs

2022-01-04 12:32:22.924Z WARN c.m.a.a.i.t.BatchSpanProcessor - Queuing span: Queue is full (future warnings will be aggregated and logged once every 5 minutes)