Skip to content

Commit 9a89dc5

Browse files
authored
Latency is measured in seconds or milliseconds
m/s would be meter per seconds that is a speed. the latency unit should be milliseconds (ms)
1 parent 4ce7c5c commit 9a89dc5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/firewall/logs-and-metrics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -185,7 +185,7 @@ The following metrics are available for Azure Firewall:
185185

186186
- **AZFW Latency Probe** - Estimates Azure Firewall average latency.
187187

188-
Unit: m/s
188+
Unit: ms
189189

190190
This metric measures the overall or average latency of Azure Firewall. Administrators can use this metric for the following purposes:
191191

@@ -198,7 +198,7 @@ The following metrics are available for Azure Firewall:
198198
This metric doesn't measure end-to-end latency of a given network path. In other words, this latency health probe doesn't measure how much latency Azure Firewall adds.
199199

200200
- When the latency metric isn't functioning as expected, a value of 0 appears in the metrics dashboard.
201-
- As a reference, the average expected latency for a firewall is approximately 1 m/s. This may vary depending on deployment size and environment.
201+
- As a reference, the average expected latency for a firewall is approximately 1 ms. This may vary depending on deployment size and environment.
202202
- The latency probe is based on Microsoft's Ping Mesh technology. So, intermittent spikes in the latency metric are to be expected. These spikes are normal and don't signal an issue with the Azure Firewall. They're part of the standard host networking setup that supports the system.
203203

204204
As a result, if you experience consistent high latency that last longer than typical spikes, consider filing a Support ticket for assistance.

0 commit comments

Comments
 (0)