Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
2,868 questions
Cosmos DB metric incorrect
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 56.00000000000001%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
Dave Lewis
25
Reputation points
Hi folks,
I've found a metric in my environment (ServiceAvailability) that is clearly just wrong in some way.
By the looks of things either Total is incorrect (should be 4400) or Count is incorrect (should be 1), which is then throwing out the Average. Either that or Minimum is wrong (but I suspect not as I'm not aware of any issues with the resource).
I can't seem to raise a support request, is there anywhere I can raise a bug instead?
Cheers
{count} votes
-
Stanislav Zhelyazkov 21,506 Reputation points MVP2024-05-13T11:48:52.5133333+00:00 Hi,
There is no other way than logging a support request. From what I can see the Average value is based on the Total divided by the Count. Total seems to represent more like average where it is unclear exactly what Average represents. So if you are looking to monitor that metrics I would choose the Total value not going below 100.
If we abstract from this specific case - Count is the number of records (entries) of the metric. Total is the sum of all values for the records. Average is divide between Total and Count.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 41%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
AnuragSingh-MSFT 20,831 Reputation points2024-05-14T09:56:44.13+00:00 @Dave Lewis, Following-up to check if you had a chance to review the answer provided.
If the answer did not help, please add more context/follow-up question for it. Else, if the answer helped, please click Accept answer so that it can help others in the community looking for help on similar topics.
-
Dave Lewis 25 Reputation points
2024-05-15T09:30:34.23+00:00 It answers the specific question I had. If there is a way of raising a bug without being able to raise a support request: No
However the underlying issue remains, and as far as I can tell there is no way of remedying it.
If it's Microsoft's position that this is answered then feel free to mark it as answered. However I personally won't really consider it answered until there is a way forward to getting it fixed.
If there is no way of tracking or raising bugs, I would have thought that having an open question about the issue would be the next best thing for anyone running into the problem in future?
-
AnuragSingh-MSFT 20,831 Reputation points
2024-05-28T05:58:51.3433333+00:00 @Dave Lewis, apologies for the inconvenience.
I reached out to CosmosDB PG with this information and got confirmation that they are working on the Metric-to-Log forwarding using the diagnostic settings. At the moment, metrics are not supported to be forwarded to LA workspace using Diagnostic Settings and the respective doc will be updated soon. Not supported in this case means that the feature may work in current form but cannot be relied on for accuracy.
Once the backlog related to metric-to-log is addressed, this feature should start working as expected and the discrepancy would be addressed. Thank you very much for bringing it to our attention.
Sign in to comment