Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Merge pull request #3445 from richrundmsft/patch-1

Update operational-insights-collect-data.md
  • Loading branch information...
commit 9f7a6330150f6b87f19ebf1b54f8d0277a6e8224 2 parents cdb3c54 + 4729d70
@tysonn tysonn authored
Showing with 41 additions and 33 deletions.
  1. +41 −33 articles/operational-insights-collect-data.md
View
74 articles/operational-insights-collect-data.md
@@ -17,17 +17,17 @@
ms.author="banders"/>
#Collect machine data
-Operational Insights uses data from servers in your on-premise or cloud infrastructure. You can collect machine data from the following sources:
+Operational Insights uses data from servers in your on-premises or cloud infrastructure. You can collect machine data from the following sources:
-- Operations Manager agents
+- Microsoft System Center Operations Manager agents
- Computers connected directly to Operational Insights
-- Virtual machine diagnostic data in Azure Storage services
+- Azure storage when generated by Azure diagnostics
After data is collected, it is sent to the Operational Insights service.
## Connect to Operational Insights from System Center Operations Manager
-You can connect Operational Insights to an existing System Center Operations Manager environment. This will allow you to use existing Operations Manager agents as Operational Insights agents. For additional information about using Operations Manager with Operational Insights, see [Operations Manager considerations with Operational Insights](operational-insights-operations-manager.md).
+You can connect Operational Insights to an existing System Center Operations Manager environment. This will allow you to use existing Operations Manager agents for data collection. For additional information about using Operations Manager with Operational Insights, see [Operations Manager considerations with Operational Insights](operational-insights-operations-manager.md).
If you use Operations Manager to monitor any of the following workloads, then you'll need to set Operations Manager run-as accounts for them. See [Operations Manager run-as accounts for Operational Insights](operational-insights-run-as.md) for more information about setting the accounts.
@@ -54,22 +54,24 @@ If you use Operations Manager to monitor any of the following workloads, then yo
## Connect computers directly to Operational Insights
-You can connect computers directly to Operational Insights by installing the Operational Insights agent to each computer you'd like to on board.
+You can connect computers directly to Operational Insights by installing the Operational Insights agent on the computer.
+Use the steps below for servers that are not running in Azure. Refer to the [Analyze data from servers in Microsoft Azure] section for how to install the agent on an Azure virtual machine.
###Download and install the agent
####To Download the agent setup file
1. In the **Operations Insights portal**, on the **Overview** page, click **Servers and Usage**.
1. Under **Servers connected directly**, click **configure**.
-1. Next to **Add Agents**, click the Agent link to download the setup file.
-1. In the **Primary Workspace Key** box, select the key and copy it (CTRL+C).
+1. Under **Attach Servers Directly (64 bit)**, click the Download Agent button to download the setup file.
+1. On the right of the **Workspace Id** box, click the copy icon and paste the id into notepad.
+1. On the right of the **Primary Key** box, click the copy icon and paste the id into notepad.
#### To install agent using setup
1. Run Setup to install the agent on a computer that you want to manage.
1. Select **Connect the agent to Microsoft Azure Operational Insights** and then click **Next**.
-1. When prompted, enter the information that you copied in step 4.
+1. When prompted, enter the information that you copied in steps 4 and 5.
1. When complete, the **Microsoft Management Agent** appears in **Control Panel**.
#### To install agent using the command line
@@ -78,18 +80,16 @@ Modify and then use the following example to install the agent using the command
MMASetup-AMD64.exe /C:"setup.exe /qn ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_ID=<your workspace id> OPINSIGHTS_WORKSPACE_KEY=<your workspace key> AcceptEndUserLicenseAgreement=1"
### Configure the Microsoft Monitoring Agent (Optional)
-Use the following information to enable an agent to communicate directly with the Microsoft Azure Operational Insights service. After you've configured the agent, it will register with the agent service and will get necessary configuration information and management packs that contain intelligence pack information.
+Use the following information to enable an agent to communicate directly with the Microsoft Azure Operational Insights service. After you've configured the agent, it will register with the agent service and will get the necessary configuration information and management packs that contain intelligence pack information.
-After data is collected from computers monitored by the agent, the number of computers monitored will appear in the Operational Insights portal on the Usage page under **Directly Connected Agents**. For any computer that sends data, you can view its data and assessment information in the Operational Insights portal.
-
-You can also disable the agent, if needed or you enable it using the command line or script.
+After data is collected from computers monitored by the agent, the number of computers monitored will appear in the Operational Insights portal on the Usage page under **Attach Servers Directly (64 bit)**. For any computer that sends data, you can view its data and assessment information in the Operational Insights portal.
#### To configure the agent
- After you've installed the **Microsoft Monitoring Agent**, open **Control Panel**.
- Open Microsoft Monitoring Agent and then click the Azure Operational Insights tab.
- Select **Connect to Azure Operational Insights**.
-- In the **Workspace ID** box, type the workspace ID provided in the Operational Insights portal.
-- In the Account Key box, paste the **Primary Workspace Key** that you copied when you installed the agent and then click **OK**.
+- In the **Workspace ID** box, paste the workspace ID copied from the Operational Insights portal.
+- In the Account Key box, paste the **Primary Key** copied from the Operational Insights portal and then click **OK**.
#### To disable an agent
- After installing the agent, open **Control Panel**.
@@ -115,9 +115,9 @@ If you have proxy servers or firewalls in your environment that restrict access
## Analyze data from servers in Microsoft Azure
-With Operational Insights you can quickly search event and IIS logs for cloud services and virtual machines by enabling [Diagnostics in Azure Cloud Services](operational-insights-log-collection.md). You can also get additional insights from your virtual machines by installing the Microsoft Monitoring Agent.
+With Operational Insights you can quickly search event and IIS logs for cloud services and virtual machines by enabling [Azure diagnostics](operational-insights-log-collection.md). You can also get additional insights from your virtual machines by installing the Microsoft Monitoring Agent.
-The Update Assessment, Change Tracking, and SQL Assessment intelligence packs all work with the Microsoft Monitoring Agent to provide deeper insights on your virtual machines. If you haven’t already, you can enable these intelligence packs when you’re signed into the [Operational Insights portal](https://preview.opinsights.azure.com/).
+The Update Assessment, Change Tracking, and SQL Assessment intelligence packs all work with the Microsoft Monitoring Agent to provide deeper insights on your virtual machines. If you haven’t already, you can [enable these intelligence packs](operational-insights-add-intelligence-pack.md) when you’re signed into the [Operational Insights portal](https://preview.opinsights.azure.com/).
For Azure virtual machines, there are two easy ways to enable agent-based data collection:
@@ -127,13 +127,17 @@ For Azure virtual machines, there are two easy ways to enable agent-based data c
When using agent-based collection for log data, you must configure which logs to collect in the Log Management configuration page of the [Operational Insights portal](https://preview.opinsights.azure.com/).
-If you’ve configured Operational Insights to index log data using diagnostics in Azure Cloud Services and you configure the agent to collect logs, then the same event logs will have 2 copies of the data indexed. If you have the agent installed, then you should collect log data using the agent and do not index the logs collected by diagnostics in Azure Cloud Services.
+ >[AZURE.NOTE] If you’ve configured Operational Insights to index log data using Azure diagnostics and you configure the agent to collect logs, then the same logs will be indexed twice.
+You will be charged normal data rates for both data sources.
+If you have the agent installed, then you should collect log data using the agent and not index the logs collected by Azure diagnostics.
### Microsoft Azure Management Portal
-In the [Operational Insights portal](https://preview.opinsights.azure.com/), go to your Operational Insights workspace and select the Servers tab. On the tab, you’ll see a list of your virtual machines. Select the virtual machine you want to install the agent on and then click **Enable Op Insights**.
+To install the agent for Operational Insights from the [Azure portal](https://manage.windowsazure.com/#Workspaces/OperationalInsightExtension/Workspaces), go to your Operational Insights workspace and select the **Servers** tab. On the tab, you’ll see a list of your virtual machines. Select the virtual machine you want to install the agent on and then click **Enable Op Insights**.
+
+The agent is automatically installed and configured for your Operational Insights workspace.
-The agent is installed and configured for your Operational Insights workspace.
+>[AZURE.NOTE] The [Azure VM agent] (https://msdn.microsoft.com/en-us/library/azure/dn832621.aspx) must be installed to automatically install the agent for Operational Insights.
![Image of Operational Insights Servers page](./media/operational-insights-collect-data/servers.png)
@@ -141,7 +145,7 @@ The agent is installed and configured for your Operational Insights workspace.
If you prefer scripting to make changes to your Azure virtual machines, then you can enable the Microsoft Monitoring Agent using PowerShell.
-The Microsoft Monitoring Agent is an [Azure virtual machine extension](https://msdn.microsoft.com/library/azure/dn832621.aspx) and can manage it using PowerShell, as shown in the example below.
+The Microsoft Monitoring Agent is an [Azure virtual machine extension](https://msdn.microsoft.com/library/azure/dn832621.aspx) and you can manage it using PowerShell, as shown in the example below.
Add-AzureAccount
@@ -152,22 +156,22 @@ The Microsoft Monitoring Agent is an [Azure virtual machine extension](https://m
$vm = Get-AzureVM –ServiceName $hostedService
Set-AzureVMExtension -VM $vm -Publisher 'Microsoft.EnterpriseCloud.Monitoring' -ExtensionName 'MicrosoftMonitoringAgent' -Version '1.*' -PublicConfiguration "{'workspaceId': '$workspaceId'}" -PrivateConfiguration "{'workspaceKey': '$workspaceKey' }" | Update-AzureVM -Verbose
-When configuring using PowerShell, you need to provide the Workspace ID and Workspace Key. You can find your Workspace ID and Workspace Key on the Servers and Usage page of the Operational Insights portal.
+When configuring using PowerShell, you need to provide the Workspace ID and Workspace Key. You can find your Workspace ID and Workspace Key on the **Servers and Usage** page of the Operational Insights portal.
![Image of Operational Insights Direct Agent Config](./media/operational-insights-collect-data/direct-agent-cfg.png)
-### Collect data using diagnostics in Azure Cloud Services
+### Collect data using Azure diagnostics
-Operational Insights can analyze data written by diagnostics for Azure Cloud Services to Azure Storage services. There are 2 main steps to perform:
+Operational Insights can analyze data written to Azure storage by Azure diagnostics. There are 2 main steps to perform:
- Configure the collection of diagnostic data to Azure storage
- Configure Operational Insights to analyze data in the storage account
The topics below describe how to enable collection of diagnostics data to Azure storage and then how to configure Operational Insights to analyze the data in Azure storage.
-Azure Diagnostics are Azure extensions that enables you to collect diagnostic telemetry data from a worker role, web role, or virtual machine running in Azure. The telemetry data is stored in an Azure storage account and can then be used by Operational Insights.
+Azure Diagnostics is an Azure extensions that enables you to collect diagnostic data from a worker role, web role, or virtual machine running in Azure. The data is stored in an Azure storage account and can then be used by Operational Insights.
->[AZURE.NOTE] You'll be charged normal data rates for storage and transactions when you send diagnostics to a storage account.
+>[AZURE.NOTE] You'll be charged normal data rates for storage and transactions when you send diagnostics to a storage account and for when Operational Insights reads the data from your storage account.
Azure Diagnostics can collect the following types of telemetry:
@@ -219,16 +223,20 @@ Description </b></td>
</table>
-Currently, Operational Insights is able to analyze IIS logs from Web roles and Windows Event logs from Web and Worker roles and Azure virtual machines. The logs must be in the following locations:
-
-- WADWindowsEventLogsTable (Table Storage)– Contains information from Windows Event logs.
+Currently, Operational Insights is able to analyze:
+- IIS logs from Web roles and virtual machines
+- Windows Event logs from Web roles, Worker roles and Azure virtual machines running a Windows operating system
+- Syslog from Azure virtual machines running a Linux operating system
+The logs must be in the following locations:
+- WADWindowsEventLogsTable (Table Storage) – Contains information from Windows Event logs.
- wad-iis-logfiles (Blob Storage) – Contains information about IIS logs.
-
-For virtual machines, you also have the option of installing the [Microsoft Monitoring Agent](http://go.microsoft.com/fwlink/?LinkId=517269) into your virtual machine. This will let you analyze IIS logs, Event Logs and will also allow you to perform additional analysis including configuration change tracking, and update assessment. Enable additional insights by installing the [Microsoft Monitoring Agent](http://go.microsoft.com/fwlink/?LinkId=517269).
+- LinuxsyslogVer1v0 (Table Storage) – Contains Linux syslog events.
>[AZURE.NOTE] IIS logs from Azure Websites are not currently supported.
+For virtual machines, you also have the option of installing the [Microsoft Monitoring Agent](http://go.microsoft.com/fwlink/?LinkId=517269) into your virtual machine to enable additional insights. In addition to being able to analyze IIS logs and Event Logs you will also allow be able to perform additional analysis including configuration change tracking, sql assessment and update assessment.
+
You can help us prioritize additional logs for Operational Insights to analyze by voting on our [feedback page](http://feedback.azure.com/forums/267889-azure-operational-insights/category/88086-log-management-and-log-collection-policy).
### Enable Azure diagnostics in a Web role for IIS log and event collection
@@ -278,11 +286,11 @@ The **AccountName** and **AccountKey** values are found in the Microsoft Azure M
Once the updated diagnostic configuration is applied to your cloud service and it is writing diagnostics to Azure Storage, then you are ready to configure Operational Insights.
-### Enable Azure Cloud Services diagnostics in a virtual machine for event log and IIS log collection
+### Enable Azure diagnostics in a virtual machine for event log and IIS log collection
-Use the following procedure to enable Azure Cloud Services diagnostics in a virtual machine for Event Log and IIS log collection using the Microsoft Azure management portal.
+Use the following procedure to enable Azure diagnostics in a virtual machine for Event Log and IIS log collection using the Microsoft Azure management portal.
-#### To enable Azure Cloud Services diagnostics in a virtual machine with the Azure management portal
+#### To enable Azure diagnostics in a virtual machine with the Azure management portal
1. Install the VM Agent when you create a virtual machine. If the virtual machine already exists, verify that the VM Agent is already installed.
- If you use the default Azure management portal to create the virtual machine, perform a **Custom Create** and select **Install the VM Agent**.
Please sign in to comment.
Something went wrong with that request. Please try again.