Hello Kulkarni, I hope you are doing well.
Thanks for reaching out to Microsoft Q&A
I have seen this case before you can take a look at someone asking a similar question
Please check this guide to troubleshoot the issue;
- Use
AzureDiagnostics
instead ofPerf
directly if possible Some of the limit counters (likememoryLimitBytes
,cpuLimitNanoCores
) show up inAzureDiagnostics
logs more reliably. - Enable capture on Event Hub for testing Temporarily enable capture to Azure Blob directly from Event Hub, inspect raw events for limits data.
- Explicitly define ASA schema In ASA, manually define input schema and include the missing counters like
memoryLimitBytes
,cpuLimitNanoCores
. - Log all incoming events in ASA Add an additional output for raw input logging in ASA to a separate Blob or Table to help isolate schema/filter issues.
- Temporarily increase Event Hub partition count Even if only for testing, try scaling to 2-4 partitions, especially if ingestion is near the throughput unit limit.
- Recheck diagnostic data export timing Limits might be present only every few intervals, so your export pipeline must stay in sync with the full diagnostic interval range.
- Consider Azure Monitor Metrics exporter For precision, sometimes using Azure Monitor Metrics → Event Hub (instead of diagnostic settings) captures limits more reliably.
😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!