Skip to content

Commit 527877f

Browse files
committed
Learn Editor: Update vminsights-log-query.md
1 parent 895aac3 commit 527877f

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/azure-monitor/vm/vminsights-log-query.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,6 @@ Every record in VMBoundPort is identified by the following fields:
131131
|Ip | Port IP address (can be wildcard IP, *0.0.0.0*) |
132132
|Port |The Port number |
133133
|Protocol | The protocol. Example, *tcp* or *udp* (only *tcp* is currently supported).|
134-
135134
The identity a port is derived from the above five fields and is stored in the PortId property. This property can be used to quickly find records for a specific port across time.
136135

137136
#### Metrics
@@ -428,7 +427,7 @@ let remoteMachines = remote | summarize by RemoteMachine;
428427
```
429428

430429
## Performance records
431-
Records with a type of *InsightsMetrics* have performance data from the guest operating system of the virtual machine. These records have the properties in the following table:
430+
Records with a type of *InsightsMetrics* have performance data from the guest operating system of the virtual machine. These records are collected at a sampling frequency of 60 second intervals and have the properties in the following table:
432431

433432

434433
| Property | Description |
@@ -468,8 +467,10 @@ The performance counters currently collected into the *InsightsMetrics* table ar
468467
| LogicalDisk | BytesPerSecond | Logical Disk Bytes Per Second | BytesPerSecond | mountId - Mount ID of the device |
469468

470469

470+
471471
## Next steps
472472

473473
* If you're new to writing log queries in Azure Monitor, review [how to use Log Analytics](../logs/log-analytics-tutorial.md) in the Azure portal to write log queries.
474474

475475
* Learn about [writing search queries](../logs/get-started-queries.md).
476+

0 commit comments

Comments
 (0)