What is your primary use case for Azure Monitor?

We use the solution for the monitoring of the agent. Whatever resources we create, it will install one agent on that resource. It will collect all the matrices. It will do a detailed analysis of how much CPU, RAM, and memory should be utilized. We can get all this information by using Azure Monitor.

Our main focus is on monitoring the utilization of resources, specifically within the ARRIS environment, where we utilize MySQL as the server. We actively track metrics such as CPU and memory utilization, as well as internet usage. The primary objective is to closely monitor resource utilization, providing insights that help us determine when adjustments to resource allocations are necessary.

I use the solution to monitor the infrastructure and applications.

Azure Monitor helps with infrastructure monitoring and getting application logs.

We use the solution to develop AI technology, particularly for financial services. It involves creating a chatbot or conversational AI system.

As an Azure solution architect, I am currently assisting a client who requires a quote for a report comparison between New Relic and Azure Monitor. Given my experience with Azure Monitor, my goal is to showcase its capabilities and potentially eliminate the need for New Relic in their environment. Azure Monitor is primarily a web application that offers comprehensive monitoring capabilities for Azure resources. It encompasses various aspects, including logging and application insights. With Azure Monitor, you can configure alerts and rules based on specific conditions, such as triggering an alert when CPU usage exceeds 80%. The cost of alerts and notifications in Azure Monitor is relatively affordable, typically charging around 10 cents per alert per rule, allowing for a large volume of SMS notifications, such as up to a hundred thousand. Comparatively, New Relic also offers cost-effective solutions. However, it is important to note that New Relic's pricing structure includes charges for user creation. Normal user creation can cost around $50, while admin users may incur a charge of approximately $99. On the other hand, when using Azure Monitor, if your organization already has an Azure subscription with Azure Active Directory (AD), you can leverage the existing user access and permissions, granting appropriate rights and access to the Azure portal as needed.

Azure Monitor is utilized for observability purposes, specifically for monitoring and alerting Azure states to customers.

We haven't yet implemented it in my current company. It's going to be for our clients. We're an MSP, and we'll be implementing it for some of our clients. The only thing that we're thinking about is using it for performance monitoring and storage monitoring. Its use case is most likely going to be to manage data. We're building out a cloud plan. We're trying to pick our own. We're trying to move certain companies into the cloud. There is a debate going on about taking the Microsoft route rather than the AWS route or the Google route. If we're going to go with Azure, we would need a monitoring tool.

We primarily use the solution for Application Insights logging, Database logging, etc. We also use it to analyze charts on the dashboard to get an overview of the issues found in the logs. The solution helps us in monitoring, analytics, and logging.

We use it for proactive infrastructure monitoring. It's being used for monitoring the key metrics and availability of infrastructure. We most probably use its latest version.

I mainly use Azure Monitor to monitor my WordPress site for availability, performance, and error logs.

I am an Azure architect and present the solution to customers for use in monitoring infrastructures, applications, and containers.

Our company is a service integrator and we use the solution to monitor logs, metrics, and applications for customers. We have 200 users throughout our company.

We use Azure Monitor to log all the activity logs and the resource logs to something similar to AWS CloudWatch. It is enabled for most of the services as it goes hand in hand with application insights. Alerts are set up using robust metrics that we are able to retrieve from Azure Monitor, allowing us to automate and look at different rules and action groups. Our component configuration keeps changing. Because of this, we need to put alerts on the components to figure out who changed them and what did they changed in them. We have been using Azure Monitor quite regularly, both for internal usage and for our customers. Customers will have to use Log Analytics in combination with Azure Monitor.

The solution is included in all of our solutions created with ISO. We always include Azure Monitor as the primary service to review the infrastructure state for our customers.

We use this solution for basically everything. For example, we use it for infrastructure, application and resource monitoring.

We use the solution for only production monitoring mainly, however, we are trying to engage it with the quality flows for moving the code between platforms from dev to test environments, et cetera. We'll implement this procedure afterward.

I use Azure Monitors and Azure monitoring to monitor our applications. It is used for balancing how your servers are working and how your servers are responding to the end user in the form of your inputs and output responses, your gate input responses and post request, and how your server is working about the workload, et cetera. We can monitor all of this by using Azure monitoring tools. There are some application insights also that we can use to put in more detailed metrics as related to the logs and the failure of the servers, and downtime, et cetera.

My client used Azure Monitor to monitor the environment in Azure.

Azure Monitor can be used to monitor on-prem servers. You can install the agent on a server on-premise and you can pull out whatever telemetry you want. Additionally, you can install it on servers that are on the public cloud. It's similar to hybrid solutions. However, it depends on the use case. If there's a server on-premise, you deploy the server in AWS or GCP. If the server is on Azure itself, then it plugs directly in which is a hybrid setup. Azure Monitor can be used if you are trying to look for how all the applications are tied together, such as application mapping. It helps to know what ports are open, what services are running on certain servers as one. We are able to monitor CPU utilization for specific servers to determine if they are running specific types of workloads or high resource utilization type workloads. We use Azure Monitor to be able to see if the server gets to a certain threshold, such as 70 percent CPU utilization, then send an alert to the operation center or reliability center to go look at it. They could then expand or increase the CPU resource there to fix the issue. The tool is used for monitoring purposes.

We use Azure Monitor as our alert system. We also use it for other types of measurement.

We all use Microsoft in the company and we are customers of Azure Monitor.

I use the SaaS version. I use Azure Monitor to collect and index logs for my systems. It allows me to search through my logs and find bugs and mistakes. From there, it helps me report these mistakes. We use this solution every day. I plan on continuing to use this solution for specific parts of projects but for other portions of my projects, I plan on using DataDog or something similar.

We're using Azure Monitor end connection as a hybrid model where it's integrated into Dynatrace. Azure Monitor monitors the infrastructure of Azure within our cloud environment. It doesn't give you any explanations or anything like that. It's just metrics, just data. We've integrated this data into Dynatrace so that the Dynatrace system and AI can give accurate response times, performance on metrics, and things like that.

We primarily use the solution as a Server monitoring service.

We are a consulting firm and we have a lot of experience with Microsoft Azure solutions. The Azure Monitor is one of the products that we implement for our clients.

Our use case for this solution is application monitoring using the Insights app. We have about five specialists in our operations team and we also have an application management team of around 10 people. There are plans to increase usage but that's something that is driven by the customers that we provide our services to. We partner with Azure Monitor and I work as a SW technologist and process unit manager in the company.

We are using multiple monitoring tools at the moment and are looking for a single solution that can monitor everything. As part of our current setup, we are using Azure Monitor to monitor our network. It ensures that our network is responding correctly and looks to see if there are any anomalies.

We use it to monitor all the services and applications, whether it is running or whether it is standing still. We use it to monitor the server and all of the CPUs so you can audit the bandwidth that has been consumed - all the day to day administrative stuff.

I use Monitor for up-down (up time / down time) monitoring and tracking performance events within Azure. Essentially, I use it for log analytic searches, backend searches, and also to provide insights into Azure Monitor.

We have a financial application that needs to be working, and for our organization, it's important to be able to see the status of the overall application, which we have now. That's our primary use case for the solution.

We are doing the Azure cloud transformation by moving to link up the application to the cloud. Monitoring is one part of application's transformation. I only work with the cloud-based model.

We are an operation center so we use this solution mainly to monitor all of our clients' environments and to help them with technical issues. So it's mainly promoting clients' environments, technical issues, and being proactive.