Merge pull request #48594 from DCtheGeek/dmc-automation-dsc-2

State Configuration changes

Author: v-shils

articles/automation/TOC.yml

@@ -131,21 +131,21 @@
           href: automation-linux-hrw-install.md
         - name: Run runbooks on a Hybrid Runbook Worker
           href: automation-hrw-run-runbooks.md
-    - name: Deploy configuration management (DSC)
+    - name: State Configuration
       items:
-        - name: Desired State Configuration (DSC) overview
+        - name: State Configuration overview
           href: automation-dsc-overview.md
         - name: Getting started
           href: automation-dsc-getting-started.md
-        - name: Configure servers to a desired state and manage drift with Azure Automation
+        - name: Configure servers to a desired state and manage drift with State Configuration
           href: tutorial-configure-servers-desired-state.md
         - name: Onboarding machines for management
           href: automation-dsc-onboarding.md
         - name: Compiling DSC configurations
           href: automation-dsc-compile.md
         - name: Continuous deployment using Chocolatey
           href: automation-dsc-cd-chocolatey.md
-        - name: Forward Azure Automation DSC reporting data to OMS Log Analytics
+        - name: Forward State Configuration reporting data to Log Analytics
           href: automation-dsc-diagnostics.md
     - name: Manage shared resources
       items:

articles/automation/automation-dsc-cd-chocolatey.md

@@ -1,35 +1,35 @@
 ---
-title: Forward Azure Automation DSC reporting data to Log Analytics
-description: This article demonstrates how to send Desired State Configuration (DSC) reporting data to Log Analytics to deliver additional insight and management.
+title: Forward Azure Automation State Configuration reporting data to Log Analytics
+description: This article demonstrates how to send Desired State Configuration (DSC) reporting data from Azure Automation State Configuration to Log Analytics to deliver additional insight and management.
 services: automation
 ms.service: automation
 ms.component: dsc
-author: georgewallace
-ms.author: gwallace
-ms.date: 06/12/2018
+author: DCtheGeek
+ms.author: dacoulte
+ms.date: 08/08/2018
 ms.topic: conceptual
 manager: carmonm
 ---
-# Forward Azure Automation DSC reporting data to Log Analytics
+# Forward Azure Automation State Configuration reporting data to Log Analytics
 
-Automation can send DSC node status data to your Log Analytics workspace.  
-Compliance status is visible in the Azure portal, or with PowerShell, for nodes and for individual DSC resources in node configurations. 
-With Log Analytics you can:
+Azure Automation State Configuration can send Desired State Configuration (DSC) node status data to
+your Log Analytics workspace. Compliance status is visible in the Azure portal or with PowerShell,
+for nodes and for individual DSC resources in node configurations. With Log Analytics you can:
 
-* Get compliance information for managed nodes and individual resources
-* Trigger an email or alert based on compliance status
-* Write advanced queries across your managed nodes
-* Correlate compliance status across Automation accounts
-* Visualize your node compliance history over time
+- Get compliance information for managed nodes and individual resources
+- Trigger an email or alert based on compliance status
+- Write advanced queries across your managed nodes
+- Correlate compliance status across Automation accounts
+- Visualize your node compliance history over time
 
 ## Prerequisites
 
-To start sending your Automation DSC reports to Log Analytics, you need:
+To start sending your Automation State Configuration reports to Log Analytics, you need:
 
-* The November 2016 or later release of [Azure PowerShell](/powershell/azure/overview) (v2.3.0).
-* An Azure Automation account. For more information, see [Getting Started with Azure Automation](automation-offering-get-started.md)
-* A Log Analytics workspace with an **Automation & Control** service offering. For more information, see [Get started with Log Analytics](../log-analytics/log-analytics-get-started.md).
-* At least one Azure Automation DSC node. For more information, see [Onboarding machines for management by Azure Automation DSC](automation-dsc-onboarding.md)
+- The November 2016 or later release of [Azure PowerShell](/powershell/azure/overview) (v2.3.0).
+- An Azure Automation account. For more information, see [Getting Started with Azure Automation](automation-offering-get-started.md)
+- A Log Analytics workspace with an **Automation & Control** service offering. For more information, see [Get started with Log Analytics](../log-analytics/log-analytics-get-started.md).
+- At least one Azure Automation State Configuration node. For more information, see [Onboarding machines for management by Azure Automation State Configuration](automation-dsc-onboarding.md)
 
 ## Set up integration with Log Analytics
 
@@ -41,61 +41,67 @@ To begin importing data from Azure Automation DSC into Log Analytics, complete t
 
   ```powershell
   # Find the ResourceId for the Automation Account
-  Find-AzureRmResource -ResourceType "Microsoft.Automation/automationAccounts"
+  Find-AzureRmResource -ResourceType 'Microsoft.Automation/automationAccounts'
   ```
+
 1. Get the _ResourceId_ of your Log Analytics workspace by running the following PowerShell command:
   (if you have more than one workspace, choose the _ResourceID_ for the workspace you want to configure).
 
   ```powershell
   # Find the ResourceId for the Log Analytics workspace
-  Find-AzureRmResource -ResourceType "Microsoft.OperationalInsights/workspaces"
+  Find-AzureRmResource -ResourceType 'Microsoft.OperationalInsights/workspaces'
   ```
+
 1. Run the following PowerShell command, replacing `<AutomationResourceId>` and `<WorkspaceResourceId>` with the _ResourceId_ values from each of the previous steps:
 
   ```powershell
-  Set-AzureRmDiagnosticSetting -ResourceId <AutomationResourceId> -WorkspaceId <WorkspaceResourceId> -Enabled $true -Categories "DscNodeStatus"
+  Set-AzureRmDiagnosticSetting -ResourceId <AutomationResourceId> -WorkspaceId <WorkspaceResourceId> -Enabled $true -Categories 'DscNodeStatus'
   ```
 
-If you want to stop importing data from Azure Automation DSC into Log Analytics, run the following PowerShell command.
+If you want to stop importing data from Azure Automation State Configuration into Log Analytics, run the following PowerShell command:
 
 ```powershell
-Set-AzureRmDiagnosticSetting -ResourceId <AutomationResourceId> -WorkspaceId <WorkspaceResourceId> -Enabled $false -Categories "DscNodeStatus"
+Set-AzureRmDiagnosticSetting -ResourceId <AutomationResourceId> -WorkspaceId <WorkspaceResourceId> -Enabled $false -Categories 'DscNodeStatus'
 ```
 
-## View the DSC logs
+## View the State Configuration logs
 
-After you set up integration with Log Analytics for your Automation DSC data, a **Log search** button will appear on 
-the **DSC Nodes** blade of your automation account. Click the **Log Search** button to view the logs for DSC node data.
+After you set up integration with Log Analytics for your Automation State Configuration data, a
+**Log search** button will appear on the **DSC Nodes** blade of your automation account. Click the
+**Log Search** button to view the logs for DSC node data.
 
 ![Log search button](media/automation-dsc-diagnostics/log-search-button.png)
 
-The **Log Search** blade opens, and you see a **DscNodeStatusData** operation for each DSC node,
-and a **DscResourceStatusData** operation for each [DSC resource](https://msdn.microsoft.com/powershell/dsc/resources)
-called in the Node configuration applied to that node.
+The **Log Search** blade opens, and you see a **DscNodeStatusData** operation for each State
+Configuration node, and a **DscResourceStatusData** operation for each [DSC
+resource](/powershell/dsc/resources) called in the Node configuration applied to that node.
 
 The **DscResourceStatusData** operation contains error information for any DSC resources that failed.
 
 Click each operation in the list to see the data for that operation.
 
 You can also view the logs by [searching in Log Analytics. 
 See [Find data using log searches](../log-analytics/log-analytics-log-searches.md).
-Type the following query to find your DSC logs:
-`Type=AzureDiagnostics ResourceProvider="MICROSOFT.AUTOMATION" Category = "DscNodeStatus"`
+Type the following query to find your State Configuration logs:
+`Type=AzureDiagnostics ResourceProvider='MICROSOFT.AUTOMATION' Category='DscNodeStatus'`
 
 You can also narrow the query by the operation name. For example:
-`Type=AzureDiagnostics ResourceProvider="MICROSOFT.AUTOMATION" Category = "DscNodeStatus" OperationName = "DscNodeStatusData"
+`Type=AzureDiagnostics ResourceProvider='MICROSOFT.AUTOMATION' Category='DscNodeStatus' OperationName='DscNodeStatusData'`
 
-### Send an email when a DSC compliance check fails
+### Send an email when a State Configuration compliance check fails
 
-One of our top customer requests is for the ability to send an email or a text when something goes wrong with a DSC configuration.   
+One of our top customer requests is for the ability to send an email or a text when something goes
+wrong with a DSC configuration.
 
-To create an alert rule, you start by creating a log search for the DSC report records that should invoke the alert.  Click the **+ New Alert Rule** button to create and configure the alert rule.
+To create an alert rule, you start by creating a log search for the State Configuration report
+records that should invoke the alert. Click the **+ New Alert Rule** button to create and configure
+the alert rule.
 
 1. From the Log Analytics Overview page, click **Log Search**.
-1. Create a log search query for your alert by typing the following search into the query field:  `Type=AzureDiagnostics Category=DscNodeStatus NodeName_s=DSCTEST1 OperationName=DscNodeStatusData ResultType=Failed`
+1. Create a log search query for your alert by typing the following search into the query field:  `Type=AzureDiagnostics Category='DscNodeStatus' NodeName_s='DSCTEST1' OperationName='DscNodeStatusData' ResultType='Failed'`
 
-  If you have set up logs from more than one Automation account or subscription to your workspace, you can group your alerts by subscription and Automation account.  
-  Automation account name can be derived from the Resource field in the search of DscNodeStatusData.  
+   If you have set up logs from more than one Automation account or subscription to your workspace, you can group your alerts by subscription and Automation account.  
+   Automation account name can be derived from the Resource field in the search of DscNodeStatusData.  
 1. To open the **Create rule** screen, click **+ New Alert Rule** at the top of the page. For more information on the options to configure the alert, see [Create an alert rulelert](../monitoring-and-diagnostics/monitor-alerts-unified-usage.md).
 
 ### Find failed DSC resources across all nodes
@@ -104,7 +110,7 @@ One advantage of using Log Analytics is that you can search for failed checks ac
 To find all instances of DSC resources that failed.
 
 1. From the Log Analytics Overview page, click **Log Search**.
-1. Create a log search query for your alert by typing the following search into the query field:  `Type=AzureDiagnostics Category=DscNodeStatus OperationName=DscResourceStatusData ResultType=Failed`
+1. Create a log search query for your alert by typing the following search into the query field:  `Type=AzureDiagnostics Category='DscNodeStatus' OperationName='DscResourceStatusData' ResultType='Failed'`
 
 ### View historical DSC node status
 
@@ -183,16 +189,22 @@ Diagnostics from Azure Automation creates two categories of records in Log Analy
 
 ## Summary
 
-By sending your Automation DSC data to Log Analytics, you can get better insight into the status of your Automation DSC nodes by:
+By sending your Automation State Configuration data to Log Analytics, you can get better insight
+into the status of your Automation State Configuration nodes by:
 
-* Setting up alerts to notify you when there is an issue
-* Using custom views and search queries to visualize your runbook results, runbook job status, and other related key indicators or metrics.  
+- Setting up alerts to notify you when there is an issue
+- Using custom views and search queries to visualize your runbook results, runbook job status, and other related key indicators or metrics.  
 
-Log Analytics provides greater operational visibility to your Automation DSC data and can help address incidents more quickly.  
+Log Analytics provides greater operational visibility to your Automation State Configuration data
+and can help address incidents more quickly.
 
 ## Next steps
 
-* To learn more about how to construct different search queries and review the Automation DSC logs with Log Analytics, see [Log searches in Log Analytics](../log-analytics/log-analytics-log-searches.md)
-* To learn more about using Azure Automation DSC, see [Getting started with Azure Automation DSC](automation-dsc-getting-started.md)
-* To learn more about Log Analytics and data collection sources, see [Collecting Azure storage data in Log Analytics overview](../log-analytics/log-analytics-azure-storage.md)
-
+- For an overview, see [Azure Automation State Configuration](automation-dsc-overview.md)
+- To get started, see [Getting started with Azure Automation State Configuration](automation-dsc-getting-started.md)
+- To learn about compiling DSC configurations so that you can assign them to target nodes, see [Compiling configurations in Azure Automation State Configuration](automation-dsc-compile.md)
+- For PowerShell cmdlet reference, see [Azure Automation State Configuration cmdlets](/powershell/module/azurerm.automation/#automation)
+- For pricing information, see [Azure Automation State Configuration pricing](https://azure.microsoft.com/pricing/details/automation/)
+- To see an example of using Azure Automation State Configuration in a continuous deployment pipeline, see [Continuous Deployment Using Azure Automation State Configuration and Chocolatey](automation-dsc-cd-chocolatey.md)
+- To learn more about how to construct different search queries and review the Automation State Configuration logs with Log Analytics, see [Log searches in Log Analytics](../log-analytics/log-analytics-log-searches.md)
+- To learn more about Log Analytics and data collection sources, see [Collecting Azure storage data in Log Analytics overview](../log-analytics/log-analytics-azure-storage.md)