Application logs: the logs developers send from applications to Azure Monitor Logs.Platform logs: the native logs of the Azure platform, made up of activity logs and resource logs.Within Microsoft Azure, there are two types of logs: We will focus on Azure Monitor logs in this article. Azure Monitor Logs: a comprehensive platform that allows you to aggregate and analyze logs.Azure Monitor Metrics: used to analyze resource metrics and automate actions if the metrics exceed certain thresholds.

The tool provides a lot of flexibility and opportunities to automate many Azure processes.Īzure Monitor consists of two sub-services:

It is a powerful tool that helps you set up self-healing and scalable application architectures. The Azure Monitor is Azure’s native service for all logging and monitoring needs. Without logs, engineering teams are hamstrung as they attempt to analyze and trace problems to fix issues. A new teammate could accidentally delete an important resource. Developers and cloud architects can misconfigure a resource, making an application vulnerable to attacks.

You also need to consider scenarios where human error could impact application health and security. This means that even while you are using Azure’s resources, you still have a responsibility to watch Azure resource usage as well as maintain your application’s performance and security.Īlthough Azure maintains responsibility for its resources’ basic health, it’s still possible for Azure resources to go offline. Shared Responsibility and the Cruciality of LoggingĪzure has a shared responsibility model. Part 3: Security Concepts and Best Practices.Explore the complete Azure Logging Guide series:

Azure ad audit logs