Skip to content

Commit af35009

Browse files
authored
Merge pull request #200674 from rakeshrana44/patch-1
Add public metrics documentation about IEC vs SI
2 parents 0a5b057 + 035c61d commit af35009

File tree

3 files changed

+36
-0
lines changed

3 files changed

+36
-0
lines changed
118 KB
Loading
213 KB
Loading

articles/azure-monitor/essentials/metrics-troubleshoot.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,42 @@ Azure metrics charts use dashed line style to indicate that there is a missing v
8181
> [!NOTE]
8282
> If you still prefer a line chart for your metric, moving mouse over the chart may help to assess the time granularity by highlighting the data point at the location of the mouse pointer.
8383
84+
## Units of measure in metrics charts
85+
86+
Azure monitor metrics uses SI based prefixes. Metrics will only be using IEC prefixes if the resource provider has chosen an appropriate unit for a metric.
87+
For ex: The resource provider Network interface (resource name: rarana-vm816) has no metric unit defined for "Packets Sent". The prefix used for the metric value here is k representing kilo (1000), a SI prefix.
88+
![Screenshot that shows metric value with prefix kilo.](./media/metrics-troubleshoot/prefix-si.png)
89+
90+
The resource provider Storage account (resource name: ibabichvm) has metric unit defined for "Blob Capacity" as bytes. Hence, the prefix used is mebi (1024^2), an IEC prefix.
91+
![Screenshot that shows metric value with prefix mebi.](./media/metrics-troubleshoot/prefix-iec.png)
92+
93+
SI uses decimal
94+
95+
| Value | abbreviation | SI |
96+
|:---------:|:------------:|:-------------------:|
97+
| 1000 | k | kilo |
98+
| 1000^2 | M | mega |
99+
| 1000^3 | G | giga |
100+
| 1000^4 | T | tera |
101+
| 1000^5 | P | peta |
102+
| 1000^6 | E | exa |
103+
| 1000^7 | Z | zetta |
104+
| 1000^8 | Y | yotta |
105+
106+
IEC uses binary
107+
108+
|Value | abbreviation| IEC |Legacy| |
109+
|:----:|:-----------:|:---:|:----:|:---:|
110+
|1024 | Ki |kibi | K | kilo|
111+
|1024^2| Mi |mebi | M | mega|
112+
|1024^3| Gi |gibi | G | giga|
113+
|1024^4| Ti |tebi | T | tera|
114+
|1024^5| Pi |pebi | - | |
115+
|1024^6| Ei |exbi | - | |
116+
|1024^7| Zi |zebi | - | |
117+
|1024^8| Yi |yobi | - | |
118+
119+
84120
## Chart shows unexpected drop in values
85121

86122
In many cases, the perceived drop in the metric values is a misunderstanding of the data shown on the chart. You can be misled by a drop in sums or counts when the chart shows the most-recent minutes because the last metric data points haven’t been received or processed by Azure yet. Depending on the service, the latency of processing metrics can be within a couple minutes range. For charts showing a recent time range with a 1- or 5- minute granularity, a drop of the value over the last few minutes becomes more noticeable:

0 commit comments

Comments
 (0)