log analytics - freshness

bandersmsft · bandersmsft · commit 15858f7b7436 · 2016-11-09T12:16:42.000-08:00
diff --git a/articles/log-analytics/log-analytics-network-performance-monitor.md b/articles/log-analytics/log-analytics-network-performance-monitor.md
@@ -13,15 +13,15 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 07/28/2016
+ms.date: 11/09/2016
 ms.author: banders
 
 ---
 # Network Performance Monitor (Preview) solution in OMS
 > [!NOTE]
 > This is a [preview solution](log-analytics-add-solutions.md#log-analytics-preview-solutions-and-features).
-> 
-> 
+>
+>
 
 This document describes how to set-up and use the Network Performance Monitor solution in OMS, which helps you monitor the performance of your networks-in near real-time-to detect and locate network performance bottlenecks. With the Network Performance Monitor solution, you can monitor the loss and latency between two networks, subnets or servers. Network Performance Monitor detects network issues like traffic blackholing, routing errors, and issues that conventional network monitoring methods are not able to detect. Network Performance Monitor generates alerts and notifies as and when a threshold is breached for a network link. These thresholds can be learned automatically by the system or you can configure them to use custom alert rules. Network Performance Monitor ensures timely detection of network performance issues and localizes the source of the problem to a particular network segment or device.
 
@@ -49,8 +49,8 @@ Use the basic processes to install agents at [Connect Windows computers to Log A
 
 > [!NOTE]
 > You'll need to install at least 2 agents in order to have enough data to discover and monitor your network resources. Otherwise, the solution will remain in a configuring state until you install and configure additional agents.
-> 
-> 
+>
+>
 
 ### Where to install the agents
 Before you install agents, consider the topology of your network and what parts of the network you want to monitor. We recommend that you install more than one agent for each subnet that you want to monitor. In other words, for every subnet that you want to monitor, choose two or more servers or VMs and install the agent on them.
@@ -68,8 +68,8 @@ The port opened by default is 8084. You can use a custom port by providing the p
 
 > [!NOTE]
 > The EnableRules.ps1 script configures Windows firewall rules only on the computer where the script is run. If you have a network firewall, you should make sure that it allows traffic destined for the TCP port being used by Network Performance Monitor.
-> 
-> 
+>
+>
 
 ## Configuring the solution
 Use the following information to install and configure the solution.
@@ -159,8 +159,8 @@ The solution makes use of synthetic transactions to assess the health of the net
 
 > [!NOTE]
 > Although agents communicate with each other frequently, they do not generate a lot of network traffic while conducting the tests. Agents rely only on TCP SYN-SYNACK-ACK handshake packets to determine the loss and latency -- no data packets are exchanged. During this process, agents communicate with each other only when needed and the agent communication topology is optimized to reduce network traffic.
-> 
-> 
+>
+>
 
 ## Using the solution
 This section explains all the dashboard functions and how to use them.
@@ -234,10 +234,9 @@ Now that you've read about Network Performance Monitor, let's look at a simple i
 5. All the paths between the 2 selected nodes are plotted in the topology map. You can visualize the hop-by-hop topology of routes between two nodes on the topology map. It gives you a clear picture of how many routes exist between the two nodes and what paths the data packets are taking. Network performance bottlenecks are marked in red color. You can locate a faulty network connection or a faulty network device by looking at red colored elements on the topology map.  
    ![unhealthy topology view example](./media/log-analytics-network-performance-monitor/npm-investigation05.png)
 6. The loss, latency, and the number of hops in each path can be reviewed in the **Path Details** pane. In this example, you can see that there are 3 unhealthy paths as mentioned in the pane. Use the scrollbar to view the details of those unhealthy paths.  Use the checkboxes to select one of the paths so that the topology for only one path is plotted. You can use your mouse wheel to zoom in or out of the topology map.
-   
+
    In the below image you can clearly see the root-cause of the problem areas to the specific section of the network by looking at the paths and hops in red color. Clicking on a node in the topology map reveals the properties of the node, including the FQDN, and IP address. Clicking on a hop shows the IP address of the hop.  
    ![unhealthy topology - path details example](./media/log-analytics-network-performance-monitor/npm-investigation06.png)
 
 ## Next steps
 * [Search logs](log-analytics-log-searches.md) to view detailed network performance data records.
-
diff --git a/articles/log-analytics/log-analytics-sccm.md b/articles/log-analytics/log-analytics-sccm.md
@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 08/29/2016
+ms.date: 11/09/2016
 ms.author: banders
 
 ---
@@ -37,25 +37,25 @@ The following procedure provides the Azure Management Portal with permissions to
 
 > [!NOTE]
 > You must specify permissions to OMS for Configuration Manager. Otherwise, you'll receive an error message when you use the configuration wizard in Configuration Manager.
-> 
-> 
+>
+>
 
 1. Open the [Azure portal](https://portal.azure.com/) and click **Browse** > **Log Analytics (OMS)** to open the Log Analytics (OMS) blade.  
 2. On the **Log Analytics (OMS)** blade, click **Add** to open the **OMS Workspace** blade.  
    ![OMS blade](./media/log-analytics-sccm/sccm-azure01.png)
 3. On the **OMS Workspace** blade, provide the following information and then click **OK**.
-   
+
    * **OMS Workspace**
    * **Subscription**
    * **Resource group**
    * **Location**
    * **Pricing tier**  
      ![OMS blade](./media/log-analytics-sccm/sccm-azure02.png)  
-     
+
      > [!NOTE]
      > The example above creates a new resource group. The resource group is only used to provide Configuration Manager with permissions to the OMS workspace in this example.
-     > 
-     > 
+     >
+     >
 4. Click **Browse** > **Resource groups** to open the **Resource groups** blade.
 5. In the **Resource groups** blade, click the resource group that you created above to open the &lt;resource group name&gt; settings blade.  
    ![resource group settings blade](./media/log-analytics-sccm/sccm-azure03.png)
@@ -72,7 +72,7 @@ In order to add an OMS connection, your Configuration Manager environment must h
 
 1. In the **Administration** workspace of Configuration Manager, select **OMS Connector**. This opens the **Add OMS Connection Wizard**. Select **Next**.
 2. On the **General** screen, confirm that you have done the following actions and that you have details for each item, then select **Next**.
-   
+
    1. In the Azure Management Portal, you've registered Configuration Manager as a Web Application and/or Web API app, and that you have the [client ID from the registration](../active-directory/active-directory-integrating-applications.md).
    2. In the Azure Management Portal, you've created an app secret key for the registered app in Azure Active Directory.  
    3. In the Azure Management Portal, you've provided the registered web app with permission to access OMS.  
@@ -87,8 +87,8 @@ In order to add an OMS connection, your Configuration Manager environment must h
 
 > [!NOTE]
 > You must connect OMS to the top-tier site in your hierarchy. If you connect OMS to a standalone primary site and then add a central administration site to your environment, you'll have to delete and recreate the OMS connection within the new hierarchy.
-> 
-> 
+>
+>
 
 After you have linked Configuration Manager to OMS, you can add or remove collections, and view the properties of the OMS connection.
 
@@ -126,4 +126,3 @@ When you click either one, Search opens, displaying either all of the imported g
 
 ## Next steps
 * Use [Log Search](log-analytics-log-searches.md) to view detailed information about your Configuration Manager data.
-
diff --git a/articles/log-analytics/log-analytics-security.md b/articles/log-analytics/log-analytics-security.md
@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 09/23/2016
+ms.date: 11/09/2016
 ms.author: banders
 
 ---
@@ -152,4 +152,3 @@ Using the OMS portal, you can export data to a CSV file and you can access data
 
 ## Next steps
 * [Get started with Log Analytics](log-analytics-get-started.md) to learn more about Log Analytics and get up and running in minutes.
-
diff --git a/articles/log-analytics/log-analytics-sql-assessment.md b/articles/log-analytics/log-analytics-sql-assessment.md
@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 08/11/2016
+ms.date: 11/09/2016
 ms.author: banders
 
 ---
@@ -40,17 +40,17 @@ Use the following information to install and configure the solution.
 * Agents must be installed on servers that have SQL Server installed.
 * The SQL Assessment solution requires .NET Framework 4 installed on each computer that has an OMS agent.
 * When using the Operations Manager agent with SQL Assessment, you'll need to use an Operations Manager Run-As account. See [Operations Manager run-as accounts for OMS](#operations-manager-run-as-accounts-for-oms) below for more information.
-  
+
   > [!NOTE]
   > The MMA agent does not support Operations Manager Run-As accounts.
-  > 
-  > 
+  >
+  >
 * Add the SQL Assessment solution to your OMS workspace using the process described in [Add Log Analytics solutions from the Solutions Gallery](log-analytics-add-solutions.md). There is no further configuration required.
 
 > [!NOTE]
 > After you've added the solution, the AdvisorAssessment.exe file is added to servers with agents. Configuration data is read and then sent to the OMS service in the cloud for processing. Logic is applied to the received data and the cloud service records the data.
-> 
-> 
+>
+>
 
 ## SQL Assessment data collection details
 SQL Assessment collects WMI data, registry data, performance data, and SQL Server dynamic management view results using the agents that you have enabled.
@@ -72,18 +72,18 @@ Use the following information to set the Operations Manager run-as account for S
 #### To configure the SQL Run As account in the Operations console
 > [!NOTE]
 > If you are using the OMS direct agent, rather than the SCOM agent, the management pack always runs in the security context of the Local System account. Skip steps 1-5 below, and run either the T-SQL or Powershell sample, specifying NT AUTHORITY\SYSTEM as the user name.
-> 
-> 
+>
+>
 
 1. In Operations Manager, open the Operations console, and then click **Administration**.
 2. Under **Run As Configuration**, click **Profiles**, and open **OMS SQL Assessment Run As Profile**.
 3. On the **Run As Accounts** page, click **Add**.
 4. Select a Windows Run As account that contains the credentials needed for SQL Server, or click **New** to create one.
-   
+
    > [!NOTE]
    > The Run As account type must be Windows. The Run As account must also be part of Local Administrators group on all Windows Servers hosting SQL Server Instances.
-   > 
-   > 
+   >
+   >
 5. Click **Save**.
 6. Modify and then execute the following T-SQL sample on each SQL Server Instance to grant minimum permissions required to Run As Account to perform SQL Assessment. However, you don’t need to do this if a Run As Account is already part of the sysadmin server role on SQL Server Instances.
 
@@ -165,11 +165,11 @@ If you have recommendations that you want to ignore, you can create a text file
 
 ### To identify recommendations that you will ignore
 1. Sign in to your workspace and open Log Search. Use the following query to list recommendations that have failed for computers in your environment.
-   
+
    ```
    Type=SQLAssessmentRecommendation RecommendationResult=Failed | select  Computer, RecommendationId, Recommendation | sort  Computer
    ```
-   
+
    Here's a screen shot showing the Log Search query:
    ![failed recommendations](./media/log-analytics-sql-assessment/sql-assess-failed-recommendations.png)
 2. Choose recommendations that you want to ignore. You’ll use the values for RecommendationId in the next procedure.
@@ -184,7 +184,7 @@ If you have recommendations that you want to ignore, you can create a text file
 ### To verify that recommendations are ignored
 1. After the next scheduled assessment runs, by default every 7 days, the specified recommendations are marked Ignored and will not appear on the assessment dashboard.
 2. You can use the following Log Search queries to list all the ignored recommendations.
-   
+
    ```
    Type=SQLAssessmentRecommendation RecommendationResult=Ignored | select  Computer, RecommendationId, Recommendation | sort  Computer
    ```
@@ -241,4 +241,3 @@ If you have recommendations that you want to ignore, you can create a text file
 
 ## Next steps
 * [Search logs](log-analytics-log-searches.md) to view detailed SQL Assessment data and recommendations.
-
diff --git a/articles/log-analytics/log-analytics-surface-hubs.md b/articles/log-analytics/log-analytics-surface-hubs.md
@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 08/11/2016
+ms.date: 11/09/2016
 ms.author: banders
 
 ---
@@ -47,7 +47,7 @@ InTune is a Microsoft product that allows you to centrally manage the OMS config
 4. Navigate to the OMS (Azure Operational Insights) section of the policy, and add the *Workspace ID* and *Workspace Key* to the policy.
 5. Save the policy.
 6. Associate the policy with the appropriate group of devices.
-   
+
    ![InTune policy](./media/log-analytics-surface-hubs/intune.png)
 
 InTune then syncs the OMS settings with the devices in the target group, enrolling them in your OMS workspace.
@@ -73,12 +73,11 @@ Monitoring your Surface Hubs using OMS is much like monitoring any other enrolle
 1. Sign in to the OMS portal.
 2. Navigate to the Surface Hub solution pack dashboard.
 3. Your device's health is displayed.
-   
+
    ![Surface Hub dashboard](./media/log-analytics-surface-hubs/surface-hub-dashboard.png)
 
 You can create [alerts](log-analytics-alerts.md) based on existing or custom log searches. Using the data the OMS collects from your Surface Hubs, you can search for issues and alert on the conditions that you define for your devices.
 
 ## Next steps
 * Use [Log searches in Log Analytics](log-analytics-log-searches.md) to view detailed Surface Hub data.
 * Create [alerts](log-analytics-alerts.md) to notify you when issues occur with your Surface Hubs.
-
diff --git a/articles/log-analytics/log-analytics-vmware.md b/articles/log-analytics/log-analytics-vmware.md
diff --git a/articles/log-analytics/log-analytics-wire-data.md b/articles/log-analytics/log-analytics-wire-data.md
