NEW EXAMPLE SCENARIO: Web Application Monitoring on Azure

This post has been republished via RSS; it originally appeared at: Azure Global articles.

First published on MSDN on Oct 10, 2018
Written by Shawn Gibbs and Nanette Ray from AzureCAT. Reviewed by Mike Wasson, Ed Price, and Tim Benjamin. Published by Adam Boeglin from Microsoft patterns & practices.

• Web Application Monitoring on Azure

We believe monitoring applications is a vital cloud scenario, and so we're glad to build out this content, now available on the Azure Architecture Center . This article was a long-time coming, and it bubbled up as the #1 request from our solution architects.



Platform as a service (PaaS) offerings on Azure manage compute resources for you and in some ways change how you monitor deployments. Azure includes multiple monitoring services, each of which performs a specific role. Together, these services deliver a comprehensive solution for collecting, analyzing, and acting on telemetry from your applications and the Azure resources they use.

The services that this Example Scenario includes:

• Azure App Service
• Application Insights
• Azure Monitor
• Log Analytics

This article explains the following aspects:

1. Scenario Architecture
   1. Components (services used)
2. Considerations
   1. Alternatives
   2. Scalability and availability
   3. Security
3. Pricing

Please check out the " Web Application Monitoring " article, as well as a growing library of additional Example Scenarios from Microsoft, on the Azure Architecture Center:

• Computer-aided engineering
• Decentralized trust between banks
• DevOps with containers
• CI/CD pipeline with Azure DevOps
• SAP for dev/test
• SAP for production
• E-commerce front-end
• E-commerce API management
• E-commerce product search

 
AzureCAT Guidance  
"Hands-on solutions, with our heads in the Cloud!"