Skip to content

Commit 5888f5e

Browse files
committed
fixes
1 parent de2cb06 commit 5888f5e

File tree

2 files changed

+4
-5
lines changed

2 files changed

+4
-5
lines changed

articles/azure-monitor/vm/monitor-virtual-machine-analyze.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -202,7 +202,6 @@ These annotations can be broadly classified into the following:
202202
- **Informational Annotations**: Emitted during control plane activities with no impact to VM availability. Examples include VM allocation, stop, delete, start. Usually, no additional customer action is required in response.
203203
- **Degraded Annotations**: Emitted when VM availability is detected to be at risk. Examples include when failure prediction models predict a degraded hardware component that can cause the VM to reboot at any given time. You should redeploy by the deadline specified in the annotation message to avoid any unanticipated loss of data or downtime.
204204

205-
206205
| Field | Description |
207206
|:---|:---|
208207
| targetResourceType | Type of resource for which health data is flowing |
@@ -211,7 +210,7 @@ These annotations can be broadly classified into the following:
211210
| annotationName | Name of the Annotation emitted |
212211
| reason | Brief overview of the availability impact observed by the customer |
213212
| category | Denotes whether the platform activity triggering the annotation was either planned maintenance or unplanned repair. This field is not applicable to customer/VM-initiated events.<br><br>Possible values: Planned \| Unplanned \| Not Applicable \| Null |
214-
| context | Denotes whether the activity triggering the annotation was due to an authorized user or process (customer initiated), or due to the Azure platform (platform initiated) or even activity in the guest OS that has resulted in availability impact (VM initiated).<br><br>Possible values: Platform-Initiated \| User-initiated \| VM-initiated | Not Applicable | Null |
213+
| context | Denotes whether the activity triggering the annotation was due to an authorized user or process (customer initiated), or due to the Azure platform (platform initiated) or even activity in the guest OS that has resulted in availability impact (VM initiated).<br><br>Possible values: Platform-Initiated \| User-initiated \|VM-initiated \| Not Applicable \| Null |
215214
| summary | Statement detailing the cause for annotation emission, along with remediation steps that can be taken by users |
216215

217216
See [Azure Resource Graph sample queries by table](../../governance/resource-graph/samples/samples-by-table.md?tabs=azure-cli#healthresources) for sample queries using this data.

articles/azure-monitor/vm/monitor-virtual-machine-data-collection.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -129,13 +129,13 @@ The following samples use the `Perf` table with custom performance data. For det
129129

130130
| Query | Description |
131131
|:--- |:---|
132-
| `Perf` |All Performance data |
132+
| `Perf` | All Performance data |
133133
| `Perf | where Computer == "MyComputer"` |All Performance data from a particular computer |
134134
| `Perf | where CounterName == "Current Disk Queue Length"` |All Performance data for a particular counter |
135135
| `Perf | where ObjectName == "Processor" and CounterName == "% Processor Time" and InstanceName == "_Total" | summarize AVGCPU = avg(CounterValue) by Computer` |Average CPU Utilization across all computers |
136-
| `Perf | where CounterName == "% Processor Time"` | summarize AggregatedValue = max(CounterValue) by Computer` |Maximum CPU Utilization across all computers |
136+
| `Perf | where CounterName == "% Processor Time" | summarize AggregatedValue = max(CounterValue) by Computer` |Maximum CPU Utilization across all computers |
137137
| `Perf | where ObjectName == "LogicalDisk" and CounterName == "Current Disk Queue Length" and Computer == "MyComputerName" | summarize AggregatedValue = avg(CounterValue) by InstanceName` |Average Current Disk Queue length across all the instances of a given computer |
138-
| `Perf | where CounterName == "Disk Transfers/sec"` | summarize AggregatedValue = percentile(CounterValue, 95) by Computer` |95th Percentile of Disk Transfers/Sec across all computers |
138+
| `Perf | where CounterName == "Disk Transfers/sec" | summarize AggregatedValue = percentile(CounterValue, 95) by Computer` |95th Percentile of Disk Transfers/Sec across all computers |
139139
| `Perf | where CounterName == "% Processor Time" and InstanceName == "_Total" | summarize AggregatedValue = avg(CounterValue) by bin(TimeGenerated, 1h), Computer` |Hourly average of CPU usage across all computers |
140140
| `Perf | where Computer == "MyComputer" and CounterName startswith_cs "%" and InstanceName == "_Total" | summarize AggregatedValue = percentile(CounterValue, 70) by bin(TimeGenerated, 1h), CounterName` | Hourly 70 percentile of every % percent counter for a particular computer |
141141
| `Perf | where CounterName == "% Processor Time" and InstanceName == "_Total" and Computer == "MyComputer" | summarize ["min(CounterValue)"] = min(CounterValue), ["avg(CounterValue)"] = avg(CounterValue), ["percentile75(CounterValue)"] = percentile(CounterValue, 75), ["max(CounterValue)"] = max(CounterValue) by bin(TimeGenerated, 1h), Computer` |Hourly average, minimum, maximum, and 75-percentile CPU usage for a specific computer |

0 commit comments

Comments
 (0)