Recommendation for Capturing and Storing Telemetry Data for Multi-Tier Azure Applications

Capture and Store Telemetry Data for Azure Multi-Tier Applications

Question

You have a multi-tier application that has an Azure Web Apps front end and an Azure SQL Database back end.

You need to recommend a solution to capture and store telemetry data. The solution must meet the following requirements:

-> Support using ad-hoc queries to identify baselines.

-> Trigger alerts when metrics in the baseline are exceeded.

-> Store application and database metrics in a central location.

What should you include in the recommendation?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

D

Azure Platform as a Service (PaaS) resources, like Azure SQL and Web Sites (Web Apps), can emit performance metrics data natively to Log Analytics.

The Premium plan will retain up to 12 months of data, giving you an excellent baseline ability.

There are two options available in the Azure portal for analyzing data stored in Log analytics and for creating queries for ad hoc analysis.

Incorrect Answers:

B: Intelligent Insights analyzes database performance by comparing the database workload from the last hour with the past seven-day baseline workload.

However, we need handle application metrics as well.

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/collect-azurepass-posh

To meet the requirements of capturing and storing telemetry data from a multi-tier application that has an Azure Web Apps front end and an Azure SQL Database back end, the recommended solution should include the following features:

  1. Support for ad-hoc queries to identify baselines: The solution should provide a mechanism to perform ad-hoc queries to identify baselines. This is important for analyzing data and identifying trends and patterns that can help in making informed decisions.

  2. Trigger alerts when metrics in the baseline are exceeded: The solution should provide an alerting mechanism to notify stakeholders when metrics in the baseline are exceeded. This is important for proactive monitoring and identifying potential issues before they impact the application.

  3. Store application and database metrics in a central location: The solution should store application and database metrics in a central location to provide a holistic view of the application's health and performance.

Based on these requirements, the recommended solution is Azure Application Insights. Azure Application Insights is a service that provides application performance management (APM) and logging capabilities for web applications. It allows you to monitor application performance, detect and diagnose issues, and gain insights into user behavior and usage patterns.

Azure Application Insights provides the following benefits:

  1. Ad-hoc queries: Azure Application Insights provides a query language called Kusto Query Language (KQL) that allows you to perform ad-hoc queries and visualizations on your telemetry data.

  2. Alerting: Azure Application Insights supports alerting on custom metrics and provides various options for alert notifications, such as email, SMS, and webhook.

  3. Centralized logging: Azure Application Insights provides a centralized location for storing and querying telemetry data from various sources, including web applications, mobile apps, and services.

Azure Event Hubs is a data streaming service that can be used to collect and process large volumes of event data. However, it does not provide the ad-hoc query capabilities or alerting features required by the scenario.

Azure SQL Database Intelligent Insights is a service that provides intelligent performance insights for Azure SQL databases. However, it does not provide a centralized location for storing and querying telemetry data from web applications.

Azure Log Analytics is a service that provides advanced analytics and visualization capabilities for log data. While it can be used to store and query telemetry data, it does not provide the ad-hoc query capabilities or alerting features required by the scenario.