Skip to content

Commit c4f7985

Browse files
committed
update prereqs
1 parent 305e8a8 commit c4f7985

File tree

3 files changed

+14
-17
lines changed

3 files changed

+14
-17
lines changed

articles/azure-monitor/agents/data-collection-iis.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,11 @@ To complete this procedure, you need:
1919
- Log Analytics workspace where you have at least [contributor rights](../logs/manage-access.md#azure-rbac).
2020
- [Data collection endpoint](../essentials/data-collection-endpoint-overview.md#create-a-data-collection-endpoint).
2121
- [Permissions to create Data Collection Rule objects](../essentials/data-collection-rule-overview.md#permissions) in the workspace.
22-
- A VM, Virtual Machine Scale Set, or Arc-enabled on-premises server with IIS logs.
23-
24-
- The log file must be stored on a local drive of the machine on which Azure Monitor Agent is running.
22+
- A VM, Virtual Machine Scale Set, or Arc-enabled on-premises server that runs IIS.
23+
- An IIS log file in W3C format must be stored on the local drive of the machine on which Azure Monitor Agent is running.
2524
- Each entry in the log file must be delineated with an end of line.
26-
- The log file must not allow circular logging, log rotation where the file is overwritten with new entries or renaming where a file is moved and a new file with the same name is opened.
25+
- The log file must not allow circular logging, log rotation where the file is overwritten with new entries, or renaming where a file is moved and a new file with the same name is opened.
26+
2727
## Create data collection rule to collect IIS logs
2828
The [data collection rule](../essentials/data-collection-rule-overview.md) defines:
2929

@@ -102,7 +102,7 @@ Heartbeat
102102
### Verify that IIS logs are being created
103103
Look at the timestamps of the log files and open the latest to see that latest timestamps are present in the log files. The default location for IIS log files is C:\\inetpub\\LogFiles\\W3SVC1.
104104

105-
:::image type="content" source="media/data-collection-text-log/iis-log-timestamp.png" lightbox="media/data-collection-text-log/iis-log-timestamp.png" alt-text="Screenshot of IIS log on agent machine showing the timestamp.":::
105+
:::image type="content" source="media/data-collection-text-log/iis-log-timestamp.png" lightbox="media/data-collection-text-log/iis-log-timestamp.png" alt-text="Screenshot of an IIS log, showing the timestamp.":::
106106

107107
### Verify that you specified the correct log location in the data collection rule
108108
The data collection rule will have a section similar to the following. The `logDirectories` element specifies the path to the log file to collect from the agent computer. Check the agent computer to verify that this is correct.
@@ -133,9 +133,9 @@ Open IIS Manager and verify that the logs are being written in W3C format.
133133

134134
:::image type="content" source="media/data-collection-text-log/iis-log-format-setting.png" lightbox="media/data-collection-text-log/iis-log-format-setting.png" alt-text="Screenshot of IIS logging configuration dialog box on agent machine.":::
135135

136-
Open the IIS log on the agent machine to verify logs are in W3C format.
136+
Open the IIS log file on the agent machine to verify that logs are in W3C format.
137137

138-
:::image type="content" source="media/data-collection-text-log/iis-log-format.png" lightbox="media/data-collection-text-log/iis-log-format.png" alt-text="Screenshot of an IIS log on an agent machine showing the header specifies W3C format.":::
138+
:::image type="content" source="media/data-collection-text-log/iis-log-format.png" lightbox="media/data-collection-text-log/iis-log-format.png" alt-text="Screenshot of an IIS log, showing the header, which specifies that the file is in W3C format.":::
139139

140140
### Share logs with Microsoft
141141
If everything is configured properly, but you're still not collecting log data, use the following procedure to collect diagnostics logs for Azure Monitor agent to share with the Azure Monitor group.

articles/azure-monitor/agents/data-collection-rule-azure-monitor-agent.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Monitor data from virtual machines with Azure Monitor Agent
2+
title: Collect events and performance counters from virtual machines with Azure Monitor Agent
33
description: Describes how to collect events and performance data from virtual machines by using Azure Monitor Agent.
44
ms.topic: conceptual
55
ms.date: 12/11/2022
@@ -9,21 +9,15 @@ ms.reviewer: shseth
99

1010
---
1111

12-
# Collect data from virtual machines with Azure Monitor Agent
12+
# Collect events and performance counters from virtual machines with Azure Monitor Agent
1313

1414
This article describes how to collect events and performance counters from virtual machines by using [Azure Monitor Agent](azure-monitor-agent-overview.md).
1515

1616
## Prerequisites
1717
To complete this procedure, you need:
1818

1919
- Log Analytics workspace where you have at least [contributor rights](../logs/manage-access.md#azure-rbac).
20-
- [Data collection endpoint](../essentials/data-collection-endpoint-overview.md#create-a-data-collection-endpoint).
2120
- [Permissions to create Data Collection Rule objects](../essentials/data-collection-rule-overview.md#permissions) in the workspace.
22-
- A VM, Virtual Machine Scale Set, or Arc-enabled on-premises server with the logs you want to collect.
23-
24-
- The log file must be stored on a local drive of the machine on which Azure Monitor Agent is running.
25-
- Each entry in the log file must be delineated with an end of line.
26-
- The log file must not allow circular logging, log rotation where the file is overwritten with new entries or renaming where a file is moved and a new file with the same name is opened.
2721

2822
## Create a data collection rule
2923

@@ -119,7 +113,7 @@ For sample templates, see [Azure Resource Manager template samples for data coll
119113

120114
## Filter events using XPath queries
121115

122-
Since you're charged for any data you collect in a Log Analytics workspace, you should limit data collection from your agent to only the event data that you need. The basic configuration in the Azure portal provides you with a limited ability to filter out events.
116+
You're charged for any data you collect in a Log Analytics workspace. Therefore, you should only collect the event data you need. The basic configuration in the Azure portal provides you with a limited ability to filter out events.
123117

124118
[!INCLUDE [azure-monitor-cost-optimization](../../../includes/azure-monitor-cost-optimization.md)]
125119

articles/azure-monitor/agents/data-collection-text-log.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,10 @@ To complete this procedure, you need:
1919
- [Data collection endpoint](../essentials/data-collection-endpoint-overview.md#create-a-data-collection-endpoint).
2020
- [Custom table](../logs/create-custom-table.md) to send your logs to.
2121
- [Permissions to create Data Collection Rule objects](../essentials/data-collection-rule-overview.md#permissions) in the workspace.
22-
- A machine that write logs to a text file.
22+
- A VM, Virtual Machine Scale Set, or Arc-enabled on-premises server that writes logs to a text file.
23+
- The log file must be stored on the local drive of the machine on which Azure Monitor Agent is running.
24+
- Each entry in the log file must be delineated with an end of line.
25+
- The log file must not allow circular logging, log rotation where the file is overwritten with new entries, or renaming where a file is moved and a new file with the same name is opened.
2326

2427
## Create data collection rule to collect text logs
2528

0 commit comments

Comments
 (0)