Skip to content

Commit c9a600f

Browse files
committed
fixing validation error
1 parent 9e0345c commit c9a600f

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -90,14 +90,14 @@ For more granular filtering by criteria such as event ID, you can create a custo
9090
Use the following guidance as a recommended starting point for event collection. Modify the DCR settings to filter unneeded events and add other events depending on your requirements.
9191

9292
| Source | Strategy |
93-
|--------|----------|
93+
|:---|:---|
9494
| Windows events | Collect at least **Critical**, **Error**, and **Warning** events for the **System** and **Application** logs to support alerting. Add **Information** events to analyze trends and support troubleshooting. **Verbose** events are rarely useful and typically shouldn't be collected. |
9595
| Syslog events | Collect at least **LOG_WARNING** events for each facility to support alerting. Add **Information** events to analyze trends and support troubleshooting. **LOG_DEBUG** events are rarely useful and typically shouldn't be collected. |
9696

9797
### Sample log queries: Windows events
9898

9999
| Query | Description |
100-
|---------|-------------|
100+
|:---|:---|
101101
| Event | All Windows events |
102102
| Event | where EventLevelName == "Error"` |All Windows events with severity of error |
103103
| Event | summarize count() by Source` |Count of Windows events by source |
@@ -106,7 +106,7 @@ Use the following guidance as a recommended starting point for event collection.
106106
### Sample log queries: Syslog events
107107

108108
| Query | Description |
109-
|----------|-------------|
109+
|:---|:---|
110110
| Syslog |All Syslogs |
111111
| Syslog | where SeverityLevel == "error"` |All Syslog records with severity of error |
112112
| Syslog | summarize AggregatedValue = count() by Computer` |Count of Syslog records by computer |
@@ -128,15 +128,15 @@ For guidance on creating a DCR to collect performance counters, see [Collect eve
128128
> You might choose to combine performance and event collection in the same DCR.
129129
130130
Destination | Description |
131-
|------------|-------------|
131+
|:---|:---|
132132
| Metrics | Host metrics are automatically sent to Azure Monitor Metrics. You can use a DCR to collect client metrics so that they can be analyzed together with [metrics explorer](../essentials/metrics-getting-started.md) or used with [metrics alerts](../alerts/alerts-create-new-alert-rule.md?tabs=metric). This data is stored for 93 days. |
133133
| Logs | Performance data stored in Azure Monitor Logs can be stored for extended periods. The data can be analyzed along with your event data by using [log queries](../logs/log-query-overview.md) with [Log Analytics](../logs/log-analytics-overview.md) or [log query alerts](../alerts/alerts-create-new-alert-rule.md?tabs=log). You can also correlate data by using complex logic across multiple machines, regions, and subscriptions.<br><br>Performance data is sent to the following tables:<br>VM insights - [InsightsMetrics](/azure/azure-monitor/reference/tables/insightsmetrics)<br>Other performance data - [Perf](/azure/azure-monitor/reference/tables/perf) |
134134

135135
### Sample log queries
136136
The following samples use the `Perf` table with custom performance data. For information on performance data collected by VM insights, see [How to query logs from VM insights](../vm/vminsights-log-query.md#performance-records).
137137

138138
| Query | Description |
139-
|--------|-------------|
139+
|:---|:---|
140140
| Perf | All Performance data |
141141
| Perf | where Computer == "MyComputer"` |All Performance data from a particular computer |
142142
| Perf | where CounterName == "Current Disk Queue Length"` |All Performance data for a particular counter |
@@ -156,7 +156,7 @@ Some applications write events written to a text log stored on the virtual machi
156156
The column names used here are examples only. The column names for your log will most likely be different.
157157

158158
| Query | Description |
159-
|------------|-------------|
159+
|:---|:---|
160160
| MyApp_CL | summarize count() by code` | Count the number of events by code. |
161161
| MyApp_CL | where status == "Error" | summarize AggregatedValue = count() by Computer, bin(TimeGenerated, 15m)` | Create an alert rule on any error event. |
162162

@@ -168,7 +168,7 @@ Records from the IIS log are stored in the [W3CIISLog](/azure/azure-monitor/refe
168168
### Sample log queries
169169

170170
| Query | Description |
171-
|-------------|-------------|
171+
|:---|:---|
172172
| W3CIISLog | where csHost=="www.contoso.com" | summarize count() by csUriStem` | Count the IIS log entries by URL for the host www.contoso.com. |
173173
| W3CIISLog | summarize sum(csBytes) by Computer` | Review the total bytes received by each IIS machine. |
174174

@@ -185,7 +185,7 @@ For different options to enable the Change Tracking solution on your virtual mac
185185
When you enable Change Tracking and Inventory, two new tables are created in your Log Analytics workspace. Use these tables for logs queries and log query alert rules.
186186

187187
| Table | Description |
188-
|-------|-------------|
188+
|:---|:---|
189189
| [ConfigurationChange](/azure/azure-monitor/reference/tables/configurationdata) | Changes to in-guest configuration data |
190190
| [ConfigurationData](/azure/azure-monitor/reference/tables/configurationdata) | Last reported state for in-guest configuration data |
191191

0 commit comments

Comments
 (0)