CODEWITHSUNDEEP
azure-web-app-serviceazure-monitoringazure-metrics-advisor
cateyes
cateyes

Reputation: 6158

Azure App Service metrics aggregation for requests: why are Sum and Count different?

When looking at the metrics from our app services in Azure, I'm very confused at Sum and Count's aggregation metrics for requests. They should be the same, according to the MS tech doc.

Count: The number of measurements captured during the aggregation interval.

When the metric is always captured with the value of 1, the count aggregation is equal to the sum aggregation. This scenario is common when the metric tracks the count of distinct events and each measurement represents one event. The code emits a metric record every time a new request arrives.

And this MS tech doc as well.

Though not the case in this example, Count is equal to Sum in cases where a metric is always captured with the value of 1. This is common when a metric tracks the occurrence of a transactional event--for example, the number of HTTP failures mentioned in a previous example in this article.

So, let say, for a specific period, if there are 10 HTTP requests, the count of requests is 10, then the sum of requests is also 10.

But ours are all different. Below are one web app service's Sum and Count metrices, you can see they are very different. But why? enter image description here

enter image description here

Upvotes: 3

Views: 1024

Answers (1)

Jason Pan
Jason Pan

Reputation: 21838

From offical restapi, we can see that count and sum are still different.

count

If you want more explanation, you can refer to the following post, or raise a support for help.

Related Post:

Azure App Service Metrics - How to interpret Sum vs. Count related to requests?

Upvotes: 1

Related Questions