Merge pull request #213220 from paulth1/agents-articles-batch-4

edit pass: Agents articles batch 4

Author: ShawnJackson

articles/azure-monitor/agents/agent-data-sources.md

@@ -1,6 +1,6 @@
 ---
 title: Log Analytics agent data sources in Azure Monitor
-description: Data sources define the log data that Azure Monitor collects from agents and other connected sources.  This article describes the concept of how Azure Monitor uses data sources, explains the details of how to configure them, and provides a summary of the different data sources available.
+description: Data sources define the log data that Azure Monitor collects from agents and other connected sources. This article describes how Azure Monitor uses data sources, explains how to configure them, and summarizes the different data sources available.
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
@@ -10,50 +10,54 @@ ms.reviewer: shseth
 ---
 
 # Log Analytics agent data sources in Azure Monitor
-The data that Azure Monitor collects from virtual machines with the legacy [Log Analytics](./log-analytics-agent.md) agent is defined by the data sources that you configure on the [Log Analytics workspace](../logs/data-platform-logs.md).   Each data source creates records of a particular type with each type having its own set of properties.
 
-![Log data collection](media/agent-data-sources/overview.png)
+The data that Azure Monitor collects from virtual machines with the legacy [Log Analytics](./log-analytics-agent.md) agent is defined by the data sources that you configure in the [Log Analytics workspace](../logs/data-platform-logs.md). Each data source creates records of a particular type. Each type has its own set of properties.
+
+![Diagram that shows log data collection.](media/agent-data-sources/overview.png)
 
 [!INCLUDE [Log Analytics agent deprecation](../../../includes/log-analytics-agent-deprecation.md)]
 
 > [!IMPORTANT]
-> The data sources described in this article apply only to virtual machines running the Log Analytics agent. 
+> The data sources described in this article apply only to virtual machines running the Log Analytics agent.
 
 ## Summary of data sources
-The following table lists the agent data sources that are currently available with the Log Analytics agent.  Each has a link to a separate article providing detail for that data source.   It also provides information on their method and frequency of collection. 
 
+The following table lists the agent data sources that are currently available with the Log Analytics agent. Each agent data source links to an article that provides information for that data source. It also provides information on their method and frequency of collection.
 
-| Data source | Platform | Log analytics agent | Operations Manager agent | Azure storage | Operations Manager required? | Operations Manager agent data sent via management group | Collection frequency |
+| Data source | Platform | Log Analytics agent | Operations Manager agent | Azure Storage | Operations Manager required? | Operations Manager agent data sent via management group | Collection frequency |
 | --- | --- | --- | --- | --- | --- | --- | --- |
-| [Custom logs](data-sources-custom-logs.md) | Windows |• |  | |  |  | on arrival |
-| [Custom logs](data-sources-custom-logs.md) | Linux   |• |  | |  |  | on arrival |
-| [IIS logs](data-sources-iis-logs.md) | Windows |• |• |• |  |  |depends on Log File Rollover setting |
-| [Performance counters](data-sources-performance-counters.md) | Windows |• |• |  |  |  |as scheduled, minimum of 10 seconds |
-| [Performance counters](data-sources-performance-counters.md) | Linux |• |  |  |  |  |as scheduled, minimum of 10 seconds |
-| [Syslog](data-sources-syslog.md) | Linux |• |  |  |  |  |from Azure storage: 10 minutes; from agent: on arrival |
-| [Windows Event logs](data-sources-windows-events.md) |Windows |• |• |• |  |• | on arrival |
+| [Custom logs](data-sources-custom-logs.md) | Windows |• |  | |  |  | On arrival. |
+| [Custom logs](data-sources-custom-logs.md) | Linux   |• |  | |  |  | On arrival. |
+| [IIS logs](data-sources-iis-logs.md) | Windows |• |• |• |  |  |Depends on the Log File Rollover setting. |
+| [Performance counters](data-sources-performance-counters.md) | Windows |• |• |  |  |  |As scheduled, minimum of 10 seconds. |
+| [Performance counters](data-sources-performance-counters.md) | Linux |• |  |  |  |  |As scheduled, minimum of 10 seconds. |
+| [Syslog](data-sources-syslog.md) | Linux |• |  |  |  |  |From Azure Storage is 10 minutes. From agent is on arrival. |
+| [Windows Event logs](data-sources-windows-events.md) |Windows |• |• |• |  |• | On arrival. |
 
+## Configure data sources
 
-## Configuring data sources
-To configure data sources for Log Analytics agents, go to the **Log Analytics workspaces** menu in the Azure portal and select a workspace. Click on **Agents configuration**. Select the tab for the data source you want to configure. You can follow the links in the table above to documentation for each data source and details on their configuration.
+To configure data sources for Log Analytics agents, go to the **Log Analytics workspaces** menu in the Azure portal and select a workspace. Select **Agents configuration**. Select the tab for the data source you want to configure. Use the links in the preceding table to access documentation for each data source and information on their configuration.
 
-Any configuration is delivered to all agents connected to that workspace.  You cannot exclude any connected agents from this configuration.
+Any configuration is delivered to all agents connected to that workspace. You can't exclude any connected agents from this configuration.
 
-[![Configure Windows events](media/agent-data-sources/configure-events.png)](media/agent-data-sources/configure-events.png#lightbox)
+[![Screenshot that shows configuring Windows events.](media/agent-data-sources/configure-events.png)](media/agent-data-sources/configure-events.png#lightbox)
 
+## Data collection
 
+Data source configurations are delivered to agents that are directly connected to Azure Monitor within a few minutes. The specified data is collected from the agent and delivered directly to Azure Monitor at intervals specific to each data source. See the documentation for each data source for these specifics.
 
-## Data collection
-Data source configurations are delivered to agents that are directly connected to Azure Monitor within a few minutes.  The specified data is collected from the agent and delivered directly to Azure Monitor at intervals specific to each data source.  See the documentation for each data source for these specifics.
+For System Center Operations Manager agents in a connected management group, data source configurations are translated into management packs and delivered to the management group every 5 minutes by default. The agent downloads the management pack like any other and collects the specified data. Depending on the data source, the data will either be sent to a management server, which forwards the data to the Azure Monitor, or the agent will send the data to Azure Monitor without going through the management server.
 
-For System Center Operations Manager agents in a connected management group, data source configurations are translated into management packs and delivered to the management group every 5 minutes by default.  The agent downloads the management pack like any other and collects the specified data. Depending on the data source, the data will be either sent to a management server which forwards the data to the Azure Monitor, or the agent will send the data to Azure Monitor without going through the management server. See [Data collection details for monitoring solutions in Azure](../monitor-reference.md) for details.  You can read about details of connecting Operations Manager and Azure Monitor and modifying the frequency that configuration is delivered at [Configure Integration with System Center Operations Manager](./om-agents.md).
+For more information, see [Data collection details for monitoring solutions in Azure](../monitor-reference.md). You can read about details of connecting Operations Manager and Azure Monitor and modifying the frequency that configuration is delivered at [Configure integration with System Center Operations Manager](./om-agents.md).
 
-If the agent is unable to connect to Azure Monitor or Operations Manager, it will continue to collect data that it will deliver when it establishes a connection.  Data can be lost if the amount of data reaches the maximum cache size for the client, or if the agent is not able to establish a connection within 24 hours.
+If the agent is unable to connect to Azure Monitor or Operations Manager, it will continue to collect data that it will deliver when it establishes a connection. Data can be lost if the amount of data reaches the maximum cache size for the client, or if the agent can't establish a connection within 24 hours.
 
 ## Log records
-All log data collected by Azure Monitor is stored in the workspace as records.  Records collected by different data sources will have their own set of properties and be identified by their **Type** property.  See the documentation for each data source and solution for details on each record type.
+
+All log data collected by Azure Monitor is stored in the workspace as records. Records collected by different data sources will have their own set of properties and be identified by their **Type** property. See the documentation for each data source and solution for details on each record type.
 
 ## Next steps
+
 * Learn about [monitoring solutions](../insights/solutions.md) that add functionality to Azure Monitor and also collect data into the workspace.
-* Learn about [log queries](../logs/log-query-overview.md) to analyze the data collected from data sources and monitoring solutions.  
+* Learn about [log queries](../logs/log-query-overview.md) to analyze the data collected from data sources and monitoring solutions.
 * Configure [alerts](../alerts/alerts-overview.md) to proactively notify you of critical data collected from data sources and monitoring solutions.

articles/azure-monitor/agents/agent-linux-troubleshoot.md

@@ -78,7 +78,7 @@ A clean reinstall of the agent fixes most issues. This task might be the first s
  Extra configurations | `/etc/opt/microsoft/omsagent/<workspace id>/conf/omsagent.d/*.conf`
 
  > [!NOTE]
- > Editing configuration files for performance counters and Syslog is overwritten if the collection is configured from the [agent's configuration](../agents/agent-data-sources.md#configuring-data-sources) in the Azure portal for your workspace. To disable configuration for all agents, disable collection from **Agents configuration**. For a single agent, run the following script:
+ > Editing configuration files for performance counters and Syslog is overwritten if the collection is configured from the [agent's configuration](../agents/agent-data-sources.md#configure-data-sources) in the Azure portal for your workspace. To disable configuration for all agents, disable collection from **Agents configuration**. For a single agent, run the following script:
 >
 > `sudo /opt/microsoft/omsconfig/Scripts/OMS_MetaConfigHelper.py --disable && sudo rm /etc/opt/omi/conf/omsconfig/configuration/Current.mof* /etc/opt/omi/conf/omsconfig/configuration/Pending.mof*`