Exam AZ-400 topic 3 question 7 discussion

I think answer should be Log Analytics What kind of telemetry data is being handled by Log Analytics ? -> Data related to infrastructure and network level i.e., few of them are syslogs, IIS logs, custom logs, windows events, windows and linux performance counters, etc. For more information, please refer https://docs.microsoft.com/en-us/azure/azure-monitor/azure-monitor-log-hub What kind of telemetry data is being handled by App Insights ? -> Data related to code-level application performance level i.e., few of them are ping URL tests, page view counts, page view load data, HTTP requests, dependency calls, exceptions and stack traces, custom events and metrics that you code, trace logs, AJAX calls, user and session counts, run-time exceptions, failure anomalies, abnormal rise in exceptions, etc. For more information, please refer https://docs.microsoft.com/en-us/azure/azure-monitor/azure-monitor-app-hub and https://docs.microsoft.com/en-us/azure/azure-monitor/app/troubleshoot-faq#what-telemetry-is-collected-by-application-insights

Its C, Cause in Log Analytics you can run the Queries + You can set triggers for alerts. and centralized Database Management.

The correct is D. Azure Log Analytics provides central storage capabilities. You could configure both the Web App and SQL Database to send data directly to Log Analytics.

These tools are used together but since we need a broader monitoring solution, I go with Log Analytics. Azure Application Insights: This is your application's performance and health specialist, providing automatic insights into user behavior, response times, and code-level diagnostics. It's the quickest way to understand what is happening within your application. Azure Log Analytics: This is your comprehensive data investigator for your entire system, allowing you to collect, analyze, and query logs and metrics from any source. It's the power tool for understanding how and when things happen across your infrastructure and applications through flexible queries and custom alerts.

I think D since we need both metrics UI and SQL

Log analytics for me. Someone mentioned in the comments that we cannot create alert rules in log. That is incorrect, we can create alerts on custom log queries just like insight alert rules

Both Log Analytics and Application Insights meets almost all requirements EXCEPT database Telemetry. This is only achieved via Log Analytics, while Application Insights track dependencies with SQL services, but almost no more. Answer: D. Log Analytics

Log Analytics-- Application Insights does not store data. Application Insights is a layer on top of Log Analytics aimed at application-level telemetry and uses the log data stored in Log Analytics to provide an additional bunch of features that make App Insights an Application Performance Management tool

It is C.

Does Application Insights store database metrics? I think no, but one of the requirements is "Store application and database metrics in a central location." I'm not familiar with Azure SQL Database Intelligent Insights but I assume it only cares about the database logs and metrics Azure Event Hubs, you can't use ad-hoc queries So the answer is Azure Log Analytics

Log Analytics will not "Trigger alerts when metrics in the baseline are exceeded."

C and D: While both Azure Application Insights and Log Analytics can meet the question's requirements, Microsoft likely chose to consider Log Analytics as the correct answer because it is more widely used for collecting and analyzing telemetry data in cloud environments. Log Analytics is a powerful tool that provides advanced analytics and insights to help monitor and troubleshoot cloud applications and infrastructure. Additionally, Log Analytics is highly integrated into the Azure ecosystem, making it a natural choice for this type of scenario. However, it is important to note that Azure Application Insights is also a valid and effective option for capturing and analyzing telemetry data in web applications. Both solutions can be successfully used to meet the requirements mentioned in the question.

Apparently the answer is: D. Azure Log Analytics >Collecting, storing, and analyzing log data from various sources (Multi-tier application) >Powerful query language for querying log data (Support using ad-hoc queries to identify baselines) >Alerts based on log data (Trigger alerts when metrics in the baseline are exceeded) >Centralize and correlate logs for monitoring, troubleshooting across your environment (Store application and database metrics in a central location) Azure Application Insights, focused on application performance monitoring, well-suited for monitoring web applications, APIs(doesn't fit to multi-tier applications as well as Log Analytics), and itself is not a centralized location for storing data.

from chatGPT: However, Azure Log Analytics does not provide some of the advanced application monitoring capabilities that are available in Azure Application Insights, such as automatic collection of telemetry data from web apps and services, and built-in support for identifying and diagnosing performance and availability issues.

C. From chatgpt, Based on the requirements, the best recommendation would be to use Azure Application Insights. Application Insights supports ad-hoc queries and alerting when metrics exceed baselines. It also stores application and database metrics in a central location, making it easy to monitor and analyze the data. While Azure Log Analytics could also be used to store and analyze telemetry data, it does not have built-in support for ad-hoc queries or alerting based on metrics exceeding baselines. Azure Event Hubs is primarily used for event streaming and real-time data ingestion, and while Azure SQL Database Intelligent Insights provides database performance monitoring and recommendations, it does not support monitoring of the application tier or alerting based on metrics exceeding baselines.

they have a condition "Store application and database metrics in a central location." Application Insights is not a centralised location. There for Log Analytics is correct.

This is D for sure