Merge pull request #411 from MicrosoftDocs/master

8/2/2019 AM Publish

.openpublishing.redirection.json

@@ -366,6 +366,10 @@
          "source_path": "docs/topics/high-performance-computing/index.md",
          "redirect_url": "/azure/architecture/topics/high-performance-computing",
          "redirect_document_id": true
+      }, 
+      {
+      "source_path": "docs/cloud-adoption/operations/monitor/cloud-app-howto.md",
+      "redirect_url": "/azure/architecture/cloud-adoption/operations/monitor/cloud-models-monitor-overview"
       }
   ] 
   } 

docs/cloud-adoption/migrate/azure-best-practices/migrate-best-practices-costs.md

@@ -137,10 +137,10 @@ Storage accounts can use different types of redundancy for resilience and high a
 
 **Type** | **Details** | **Usage**
 --- | --- | ---
-**Locally Redundant Storage (LRS)** | Protects against a local outage by replicating within a single storage unit to a separate fault domain and update domain. Keeps multiple copies of your data in one datacenter. Provides at least 99.999999999 % (11 9\'s) durability of objects over a given year. | Consider if your app stores data that can be easily reconstructed.
-**Zone Redundant Storage (ZRS)** | Protects again a datacenter outage by replicating across three storage clusters in a single region. Each storage cluster is physically separated and located in its own availability zone. Provides at least 99.9999999999 % (12 9\'s) durability of objects over a given year by keeping multiple copies of your data across multiple datacenters or regions. | Consider if you need consistency, durability, and high availability. Might not protect against a regional disaster when multiple zones are permanently affected.
-**Geographically Redundant Storage (GRS)** | Protects against an entire region outage by replicating data to a secondary region hundreds of miles away from the primary. Provides at least 99.99999999999999 % (16 9\'s) durability of objects over a given year. | Replica data isn't available unless Microsoft initiates a failover to the secondary region. If failover occurs, read and write access is available.
-**Read-Access Geographically Redundant Storage (RA-GRS)** | Similar to GRS. Provides at least 99.99999999999999 % (16 9\'s) durability of objects over a given year | Provides and 99.99 % read availability by allowing read access from the second region used for GRS.
+**Locally redundant storage (LRS)** | Protects against a local outage by replicating within a single storage unit to a separate fault domain and update domain. Keeps multiple copies of your data in one datacenter. Provides at least 99.999999999 % (11 9\'s) durability of objects over a given year. | Consider if your app stores data that can be easily reconstructed.
+**Zone-redundant storage (ZRS)** | Protects again a datacenter outage by replicating across three storage clusters in a single region. Each storage cluster is physically separated and located in its own availability zone. Provides at least 99.9999999999 % (12 9\'s) durability of objects over a given year by keeping multiple copies of your data across multiple datacenters or regions. | Consider if you need consistency, durability, and high availability. Might not protect against a regional disaster when multiple zones are permanently affected.
+**Geographically redundant storage (GRS)** | Protects against an entire region outage by replicating data to a secondary region hundreds of miles away from the primary. Provides at least 99.99999999999999 % (16 9\'s) durability of objects over a given year. | Replica data isn't available unless Microsoft initiates a failover to the secondary region. If failover occurs, read and write access is available.
+**Read-access geographically redundant storage (RA-GRS)** | Similar to GRS. Provides at least 99.99999999999999 % (16 9\'s) durability of objects over a given year | Provides and 99.99 % read availability by allowing read access from the second region used for GRS.
 
 **Learn more:**
 

docs/cloud-adoption/operations/monitor/alert.md

@@ -2,7 +2,7 @@
 title: Cloud monitoring guide – Alerting
 titleSuffix: Microsoft Cloud Adoption Framework for Azure
 description: Choose when to use Azure Monitor or System Center Operations Manager in Microsoft Azure
-author: mgoedtel
+author: MGoedtel
 ms.author: magoedte
 ms.date: 06/26/2019
 ms.topic: guide

docs/cloud-adoption/operations/monitor/cloud-models-monitor-overview.md

@@ -0,0 +1,59 @@
+---
+title: Cloud monitoring guide – Monitoring strategy for cloud deployment models
+titleSuffix: Microsoft Cloud Adoption Framework for Azure
+description: Choose when to use Azure Monitor or System Center Operations Manager in Microsoft Azure
+author: MGoedtel
+ms.author: magoedte
+ms.date: 07/31/2019
+ms.topic: guide
+ms.service: cloud-adoption-framework
+ms.subservice: operate
+services: azure-monitor
+---
+
+# Cloud monitoring guide: Monitoring strategy for cloud deployment models
+
+This article includes our recommended monitoring strategy for each of the cloud deployment models, based on the following criteria:
+
+- You require continued commitment to Operations Manager or other enterprise monitoring platform. This is because of integration with your IT operations processes, knowledge and expertise, or because certain functionality isn't available yet in Azure Monitor.
+- You have to monitor workloads both on-premises and in the public cloud, or just in the cloud.
+- Your cloud migration strategy includes modernizing IT operations and moving to our cloud monitoring services and solutions.
+- You might have critical systems that are air-gapped or physically isolated, hosted in a private cloud or on physical hardware, and need to be monitored.
+
+Our strategy includes support for monitoring infrastructure (compute, storage, and server workloads), application (end-user, exceptions, and client), and network resources to deliver a complete, service-oriented monitoring perspective.
+
+## Azure cloud monitoring
+
+Azure Monitor is the platform service that provides a single source for monitoring Azure resources. It's designed for cloud solutions that are built on Azure, and that support a business capability that is based on VM workloads or complex architectures that use microservices and other platform resources. It monitors all layers of the stack, starting with tenant services such as Azure Active Directory Domain Services, and subscription-level events and Azure service health. It also monitors infrastructure resources like VMs, storage, and network resources, and, at the top layer, your application. Monitoring each of these dependencies, and collecting the right signals that each can emit, gives you the observability of applications and the key infrastructure you need.
+
+The following table summarizes the recommended approach to monitoring each layer of the stack.
+
+<!-- markdownlint-disable MD033 -->
+
+Layer | Resource | Scope | Method
+---|---|---|----
+Application | Web-based application running on .NET, .NET Core, Java, JavaScript, and Node.js platform on an Azure VM, Azure App Services, Azure Service Fabric, Azure Functions, and Azure Cloud Services | Monitor a live web application to automatically detect performance anomalies, identify code exceptions and issues, and collect usability telemetry. |  Application Insights
+Containers | Azure Kubernetes Service/Azure Container Instances | Monitor capacity, availability, and performance of workloads running on containers and container instances. | Azure Monitor for containers
+Guest operating system | Linux and Windows VM operating system | Monitor capacity, availability, and performance. Map dependencies hosted on each VM, including the visibility of active network connections between servers, inbound and outbound connection latency, and ports across any TCP-connected architecture. | Azure Monitor for VMs
+Azure resources - PaaS | Azure Database services (for example, SQL or mySQL) | Azure Database for SQL performance metrics. | Enable diagnostic logging to stream SQL data to Azure Monitor Logs.
+Azure resources - IaaS | 1. Azure Storage<br/> 2. Azure Application Gateway<br/> 3. Azure Key Vault<br/> 4. Network security groups<br/> 5. Azure Traffic Manager | 1. Capacity, availability, and performance.<br/> 2. Performance and diagnostic logs (activity, access, performance, and firewall).<br/> 3. Monitor how and when your key vaults are accessed, and by whom.<br/> 4. Monitor events when rules are applied, and the rule counter for how many times a rule is applied to deny or allow.<br/>5. Monitor endpoint status availability. | 1. Storage metrics for Blob storage.<br/> 2. Enable diagnostic logging and configure streaming to Azure Monitor Logs.<br/> 3. Enable diagnostic logging and configure streaming to Azure Monitor Logs, and enable the [Azure Key Vault Analytics Solution](https://docs.microsoft.com/azure/azure-monitor/insights/azure-key-vault). <br/> 4. Enable diagnostic logging of network security groups, and configure streaming to Azure Monitor Logs.<br/> 5. Enable diagnostic logging of Traffic Manager endpoints, and configure streaming to Azure Monitor Logs.
+Network| Communication between your virtual machine and one or more endpoints (another VM, a fully qualified domain name, a uniform resource identifier, or an IPv4 address). | Monitor reachability, latency, and network topology changes that occur between the VM and the endpoint. | Azure Network Watcher
+Azure subscription | Azure service health and basic resource health | <li> Administrative actions performed on a service or resource.<br/><li> Service health with an Azure service is in a degraded or unavailable state.<br/><li> Health issues detected with an Azure resource from the Azure service perspective.<br/><li> Operations performed with Azure Autoscale indicating a failure or exception. <br/><li> Operations performed with Azure Policy indicating that an allowed or denied action occurred.<br/><li> Record of alerts generated by Azure Security Center. |Delivered in the Activity Log for monitoring and alerting by using Azure Resource Manager.
+Azure tenant|Azure Active Directory || Enable diagnostic logging, and configure streaming to Azure Monitor Logs.
+
+<!-- markdownlint-enable MD033 -->
+
+## Hybrid cloud monitoring
+
+This section is currently under development to deliver a comprehensive set of recommendations intended to address your interest for this cloud model, and will be made available shortly.  
+
+## Private cloud monitoring
+
+You can achieve holistic monitoring of Azure Stack with System Center Operations Manager. Specifically, you can monitor the workloads running in the tenant, the resource level, on the virtual machines, and the infrastructure hosting Azure Stack (physical servers and network switches). You can also achieve holistic monitoring with a combination of [infrastructure monitoring capabilities](/azure/azure-stack/azure-stack-monitor-health) included in Azure Stack. These capabilities help you view health and alerts for an Azure Stack region and the [Azure Monitor service](/azure/azure-stack/user/azure-stack-metrics-azure-data) in Azure Stack, which provides base-level infrastructure metrics and logs for most services.
+
+If you've already invested in Operations Manager, use the Azure Stack management pack to monitor the availability and health state of Azure Stack deployments. This includes regions, resource providers, updates, update runs, scale units, unit nodes, infrastructure roles, and their instances (logical entities comprised of the hardware resources). It uses the Health and Update resource provider REST APIs to communicate with Azure Stack. To monitor physical servers and storage devices, use the OEM vendors' management pack (for example, provided by Lenovo, Hewlett Packard, or Dell). Operations Manager can natively monitor the network switches to collect basic statistics by using the SNMP protocol. Monitoring the tenant workloads is possible with the Azure management pack by following two basic steps. Configure the subscription that you want to monitor, and then add the monitors for that subscription.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Collecting the right data](./data-collection.md)

docs/cloud-adoption/operations/monitor/data-collection.md

@@ -2,7 +2,7 @@
 title: Cloud monitoring guide – Collecting the right data
 titleSuffix: Microsoft Cloud Adoption Framework for Azure
 description: Choose when to use Azure Monitor or System Center Operations Manager in Microsoft Azure
-author: mgoedtel
+author: MGoedtel
 ms.author: magoedte
 ms.date: 06/26/2019
 ms.topic: guide
@@ -42,7 +42,7 @@ To drive quicker resolution of the incident, consider the following recommendati
 
 Embracing this guiding set of principles gives you near real-time insights, as well as better management of your service.
 
-## Next step
+## Next steps
 
 > [!div class="nextstepaction"]
 > [Alerting strategy](./alert.md)

docs/cloud-adoption/operations/monitor/index.md

@@ -2,9 +2,9 @@
 title: Cloud monitoring guide
 titleSuffix: Microsoft Cloud Adoption Framework for Azure
 description: Overview of Azure Monitor and System Center Operations Manager
-author: mgoedtel
+author: MGoedtel
 ms.author: magoedte
-ms.date: 06/26/2019
+ms.date: 07/31/2019
 ms.topic: guide
 ms.service: cloud-adoption-framework
 ms.subservice: operate
@@ -23,7 +23,7 @@ This digital transformation is also enabling an opportunity to modernize your in
 
 Stakeholders want to use cloud-based, software as a service (SaaS) monitoring and management tools. They need to understand what services and solutions deliver in order to achieve end-to-end visibility, reduce costs, and focus less on infrastructure and maintenance of traditional software-based IT operations tools.
 
-However, IT often prefers to use the tools they have already made a significant investment in. This supports their service operations processes to monitor both, with the eventual goal of transitioning to a SaaS-based offering. This choice is not only because it takes time planning, resources, and funding to switch. It's also due to confusion about which products or Azure services are appropriate or applicable to achieve the transition.
+However, IT often prefers to use the tools they have already made a significant investment in. This supports their service operations processes to monitor both cloud models, with the eventual goal of transitioning to a SaaS-based offering. This choice is not only because it takes time planning, resources, and funding to switch. It's also due to confusion about which products or Azure services are appropriate or applicable to achieve the transition.
 
 The goal of this guide is to provide a detailed reference to help enterprise IT managers, business decision makers, application architects, and application developers understand:
 
@@ -33,6 +33,8 @@ The goal of this guide is to provide a detailed reference to help enterprise IT
 
 This guide isn't a how-to guide for using or configuring individual Azure services and solutions, but does reference those sources when applicable or available. After reading this guide, you'll understand how to successfully operate a workload following recommended practices and patterns.
 
+If you are unfamiliar with Azure Monitor and System Center Operations Manager and you would like to get a better understanding of what makes them unique and how they compare to each other before going any further, review the [Overview of our monitoring platforms](./platform-overview.md).
+
 ## Audience
 
 This guide is primarily useful for enterprise administrators, IT operations, IT security and compliance, application architects, workload development owners, and workload operations owners.
@@ -42,8 +44,7 @@ This guide is primarily useful for enterprise administrators, IT operations, IT
 This article is part of a series. The following articles are meant to be read together, in order:
 
 * Introduction (this article)
-* [Overview of the Azure monitoring platform](./platform-overview.md)
-* [Monitoring Azure cloud applications](./cloud-app-howto.md)
+* [Monitoring strategy for cloud deployment models](./cloud-models-monitor-overview.md)
 * [Collecting the right data](./data-collection.md)
 * [Alerting](./alert.md)
 
@@ -53,14 +54,14 @@ A selection of software and services are available to monitor and manage a varie
 
 * System Center Operations Manager
 * Azure Monitor, which now includes Log Analytics and Application Insights
-* Azure Blueprints and Azure Policy
+* Azure Policy and Azure Blueprints
 * Azure Automation
 * Azure Logic Apps
 * Azure Event Hubs
 
-A large part of this guide discusses and contrasts Azure Monitor to System Center Operations Manager.
+This first version of the guide covers our current monitoring platforms - Azure Monitor and System Center Operations Manager, and outlines our recommended strategy for monitoring each of the cloud deployment models. Also included is the first set of monitoring recommendations, starting with data collection and alerting.
 
-## Next step
+## Next steps
 
 > [!div class="nextstepaction"]
-> [Overview of the Azure monitoring platform](./platform-overview.md)
+> [Monintoring strategy for cloud deployment models](./cloud-models-monitor-overview.md)