Merge pull request #67094 from msebolt/azure-monitor-rebrand-pr12

PRMerger18 · web-flow · commit 21128292ffc5 · 2019-02-22T02:48:41.000+08:00
azure monitor rebrand blockchain cdn
diff --git a/articles/blockchain/templates/ethereum-deployment.md b/articles/blockchain/templates/ethereum-deployment.md
@@ -37,9 +37,9 @@ A consortium member also has a set of load-balanced transaction nodes. These nod
 
 Transaction nodes are load-balanced within an availability set to maintain high availability. The template supports up to five transaction nodes provisioned using virtual machine scale sets.
 
-### Log analytics details
+### Azure Monitor logs details
 
-Each deployment also creates a new Log analytics instance or can join an existing instance. Log analytics allows the monitoring of various performance metrics of each virtual machine that makes up the deployed network.
+Each deployment also creates a new Azure Monitor logs instance or can join an existing instance. Azure Monitor logs allows the monitoring of various performance metrics of each virtual machine that makes up the deployed network.
 
 ## Deployment architecture
 
@@ -90,7 +90,7 @@ Operations Management Suite (OMS) allows you to configure an OMS resource for yo
 
 Parameter Name|Description| Allowed Values|Default Values
 ---|---|---|---
-Connect to existing OMS|Create a new Log Analytics instance or join an existing instance|Create new Join existing|Create new Log Analytics Location|The region where the new Log Analytics will be deployed (Visible if *Create new* is selected)
+Connect to existing OMS|Create a new Azure Monitor logs instance or join an existing instance|Create new Join existing|Create new Azure Monitor logs location|The region where the new Azure Monitor logs will be deployed (Visible if *Create new* is selected)
 Existing OMS Workspace Id|Workspace ID of the existing instance (Visible if *Join Existing* is selected) OMS Service Tier|Choose the pricing tier for the new instance. More Info at https://azure.microsoft.com/pricing/details/log-analytics/ (Visible if *Join Existing* is selected)|Free Standalone Per Node|Free
 Existing OMS Primary Key|The primary key used to connect to the existing OMS instance (Visible if *Join Existing* is selected)
 
diff --git a/articles/blockchain/templates/ethereum-poa-deployment.md b/articles/blockchain/templates/ethereum-poa-deployment.md
@@ -409,17 +409,17 @@ A sample deployment is shown below:
 
 #### Monitoring
 
-The Monitoring blade allows you to configure a Log Analytics
+The Monitoring blade allows you to configure an Azure Monitor logs
 resource for your network. The monitoring agent will collect and surface useful
 metrics and logs from your network, providing the ability to quickly
 check the network health or debug issues.
 
   Parameter name|Description|Allowed values|Default values
   ---|---|---|---
 Monitoring|Option to enable Monitoring|Enable or Disable|Enable
-Connect to existing Log Analytics|Create a new Log Analytics instance or join an existing instance|Create new or Join existing|Create new
-Monitor Location(Connect to existing Log Analytics= Create new)|The region where the new Log Analytics instance will be deployed|All Log Analytics regions|NA
-Existing Log Analytics Workspace Id (Connect to existing Log Analytics = Join Existing)|Workspace ID of the existing Log Analytics instance||NA
+Connect to existing Azure Monitor logs|Create a new Azure Monitor logs instance or join an existing instance|Create new or Join existing|Create new
+Monitor Location(Connect to existing Azure Monitor logs= Create new)|The region where the new Azure Monitor logs instance will be deployed|All Azure Monitor logs regions|NA
+Existing Log Analytics Workspace Id (Connect to existing Azure Monitor logs = Join Existing)|Workspace ID of the existing Azure Monitor logs instance||NA
 Existing Log Analytics Primary Key (Connect to existing Log Analytics = Join Existing)|The primary key used to connect to the existing Log Analytics instance||NA
 
 
@@ -588,7 +588,7 @@ statistics.
 
 ![network stats](./media/ethereum-poa-deployment/network-stats.png)
 
-#### Sample Log Analytics queries
+#### Sample Kusto queries
 
 Behind these dashboards is a set of queryable raw logs. You can use
 these raw logs to customize the dashboards, investigate failures, or
diff --git a/articles/blockchain/workbench/troubleshooting.md b/articles/blockchain/workbench/troubleshooting.md
@@ -19,7 +19,7 @@ A PowerShell script is available to assist with developer debugging or support.
 * Blockchain network, such as Ethereum
 * Blockchain Workbench microservices
 * Application Insights
-* Azure Monitoring (Log Analytics)
+* Azure Monitoring (Azure Monitor logs)
 
 You can use the information to determine next steps and determine root cause of issues.
 
@@ -47,9 +47,9 @@ The script accepts the following parameters:
 | ResourceGroupName | Name of the Azure Resource Group where Blockchain Workbench has been deployed. | Yes |
 | OutputDirectory | Path to create the output .ZIP file. If not specified, defaults to the current directory. | No |
 | LookbackHours | Number of hours to use when pulling telemetry. Default value is 24 hours. Maximum value is 90 hours | No |
-| OmsSubscriptionId | The subscription ID where Log Analytics is deployed. Only pass this parameter if the Log Analytics for the blockchain network is deployed outside of Blockchain Workbench's resource group.| No |
-| OmsResourceGroup |The resource group where Log Analytics is deployed. Only pass this parameter if the Log Analytics for the blockchain network is deployed outside of Blockchain Workbench's resource group.| No |
-| OmsWorkspaceName | The Log Analytics workspace name. Only pass this parameter if the Log Analytics for the blockchain network is deployed outside of Blockchain Workbench's resource group | No |
+| OmsSubscriptionId | The subscription ID where Azure Monitor logs is deployed. Only pass this parameter if the Azure Monitor logs for the blockchain network is deployed outside of Blockchain Workbench's resource group.| No |
+| OmsResourceGroup |The resource group where Azure Monitor logs is deployed. Only pass this parameter if the Azure Monitor logs for the blockchain network is deployed outside of Blockchain Workbench's resource group.| No |
+| OmsWorkspaceName | The Log Analytics workspace name. Only pass this parameter if the Azure Monitor logs for the blockchain network is deployed outside of Blockchain Workbench's resource group | No |
 
 ## What is collected?
 
diff --git a/articles/cdn/cdn-azure-diagnostic-logs.md b/articles/cdn/cdn-azure-diagnostic-logs.md
@@ -32,7 +32,7 @@ Azure diagnostics logs allow you to export basic usage metrics from your CDN end
 
 - Export data to blob storage, export to CSV, and generate graphs in Excel.
 - Export data to Event Hubs and correlate with data from other Azure services.
-- Export data to Log Analytics and view data in your own Log Analytics work space
+- Export data to Azure Monitor logs and view data in your own Log Analytics workspace
 
 The following diagram shows a typical CDN core analytics view of data.
 
@@ -82,15 +82,15 @@ To use a storage account to store the logs, follow these steps:
 
 5. After you have finished making your diagnostic log settings, select **Save**.
 
-### Logging with Log Analytics
+### Logging with Azure Monitor
 
-To use Log Analytics to store the logs, follow these steps:
+To use Azure Monitor to store the logs, follow these steps:
 
 1. From the **Diagnostics logs** page, select **Send to Log Analytics**. 
 
     ![portal - Diagnostics logs](./media/cdn-diagnostics-log/05_Ready-to-Configure.png)    
 
-2. Select **Configure** to configure Log Analytics logging. 
+2. Select **Configure** to configure Azure Monitor logging. 
 
    The **Log Analytics workspaces** page appears.
 
@@ -130,7 +130,7 @@ To use Log Analytics to store the logs, follow these steps:
 
     ![portal - Diagnostics logs](./media/cdn-diagnostics-log/cdn-core-analytics-page.png) 
 
-    Your Log Analytics workspace is now ready to log data. In order to consume that data, you must use a [Log Analytics Solution](#consuming-diagnostics-logs-from-a-log-analytics-workspace), covered later in this article.
+    Your Log Analytics workspace is now ready to log data. In order to consume that data, you must use a [Azure Monitor logs solution](#consuming-diagnostics-logs-from-a-log-analytics-workspace), covered later in this article.
 
 For more information about log data delays, see [Log data delays](#log-data-delays).
 
@@ -208,9 +208,9 @@ Here's how you can use the tool:
 5.	The resulting CSV file shows the analytics data in a simple flat hierarchy.
 
 ## Consuming diagnostics logs from a Log Analytics workspace
-Log Analytics is an Azure service that monitors your cloud and on-premises environments to maintain their availability and performance. It collects data generated by resources in your cloud and on-premises environments and from other monitoring tools to provide analysis across multiple sources. 
+Azure Monitor is an Azure service that monitors your cloud and on-premises environments to maintain their availability and performance. It collects data generated by resources in your cloud and on-premises environments and from other monitoring tools to provide analysis across multiple sources. 
 
-To use Log Analytics, you must [enable logging](#enable-logging-with-azure-storage) to the Azure Log Analytics workspace, which is discussed earlier in this article.
+To use Azure Monitor, you must [enable logging](#enable-logging-with-azure-storage) to the Azure Log Analytics workspace, which is discussed earlier in this article.
 
 ### Using the Log Analytics workspace
 
@@ -224,9 +224,9 @@ You can display the data in a variety of ways by using Management Solutions. You
 
 You can install management solutions from Azure marketplace by selecting the **Get it now** link at the bottom of each solution.
 
-### Add a Log Analytics CDN Management Solution
+### Add a Azure Monitor CDN Management Solution
 
-Follow these steps to add a Log Analytics Management Solution:
+Follow these steps to add a Azure Monitor Management Solution:
 
 1.   Sign in to the Azure portal using your Azure subscription and go to your dashboard.
     ![Azure dashboard](./media/cdn-diagnostics-log/13_Azure-dashboard.png)
@@ -440,7 +440,7 @@ Example properties:
 
 * [Azure Diagnostic logs](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-overview-of-diagnostic-logs)
 * [Core analytics via Azure CDN supplemental portal](https://docs.microsoft.com/azure/cdn/cdn-analyze-usage-patterns)
-* [Azure Log Analytics](https://docs.microsoft.com/azure/log-analytics/log-analytics-overview)
+* [Azure Monitor logs](https://docs.microsoft.com/azure/log-analytics/log-analytics-overview)
 * [Azure Log Analytics REST API](https://docs.microsoft.com/rest/api/loganalytics)
 
 
diff --git a/articles/cdn/cdn-log-analysis.md b/articles/cdn/cdn-log-analysis.md
@@ -24,7 +24,7 @@ After you enable CDN for your application, you can monitor CDN usage, check the
 
 ## Core analytics via Azure diagnostic logs
 
-Core analytics is available for CDN endpoints for all pricing tiers. Azure diagnostics logs allow core analytics to be exported to Azure storage, event hubs, or Azure Log Analytics. Azure Log Analytics offers a solution with graphs that are user-configurable and customizable. For more information about Azure diagnostic logs, see [Azure diagnostic logs](cdn-azure-diagnostic-logs.md).
+Core analytics is available for CDN endpoints for all pricing tiers. Azure diagnostics logs allow core analytics to be exported to Azure storage, event hubs, or Azure Monitor logs. Azure Monitor logs offers a solution with graphs that are user-configurable and customizable. For more information about Azure diagnostic logs, see [Azure diagnostic logs](cdn-azure-diagnostic-logs.md).
 
 ## Verizon core reports
 
