Some data points seem to disappear downstream when using Event hubs

Kulkarni, Yash 0 Reputation points
2025-06-01T11:18:09.73+00:00

Hi!

Let me explain my current setup to you -

  1. Setup diagnostic rule in AKS to send log data to a log analytics workspace (LAW)
  2. Setup a data export rule from to an event hub
  3. Data goes from event hub to ASA (azure stream analytics)
  4. And from ASA to blob storage

I am trying to check the 'Perf' table which has CPU & memory usage & limit details for my deployed AKS services. However, I run into the following issue -

I can see that the CPU & memory limits are present in the LAW (when checking via Azure monitor), but these rows aren't visible downstream i.e. in the blob storage. I have checked every stage of my soln to check if there are any data filters, and there are none. In LAW, I can see the following data -

User's image

But in my blob storage data (or even in the raw event hub data), the only counter names I see are memoryRssByter, cpuUsageNanoCores & restartTimeEpoch.

Can someone pls help!!

FYI - Yes, I checked the data export rule in LAW, I am just sending the Perf table as is without modifications.

I have only 1 partition in the event hub.

Also, I checked to see the frequency of these "limit" counters, and seems like there are alot of rows (~1000) every 5mins, but I have no rows in the blob yet.

Azure Event Hubs
Azure Event Hubs
An Azure real-time data ingestion service.
720 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Jose Benjamin Solis Nolasco 3,511 Reputation points
    2025-06-01T18:38:27.8733333+00:00

    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

    https://learn.microsoft.com/en-us/answers/questions/2147758/debugging-data-loss-in-stream-analytics-to-event-h

    Please check this guide to troubleshoot the issue;

    1. Use AzureDiagnostics instead of Perf directly if possible Some of the limit counters (like memoryLimitBytes, cpuLimitNanoCores) show up in AzureDiagnostics logs more reliably.
    2. Enable capture on Event Hub for testing Temporarily enable capture to Azure Blob directly from Event Hub, inspect raw events for limits data.
    3. Explicitly define ASA schema In ASA, manually define input schema and include the missing counters like memoryLimitBytes, cpuLimitNanoCores.
    4. 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.
    5. 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.
    6. 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.
    7. 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!


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.