Azure Monitor Reviews

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. 

There are a few good features in this solution. First, it's integrated with Azure DevOps. Second, it has good load gathering and very good analysis. Finally, the metrics gathering, even though it requires some actions and application level, is also fairly good.

I think the product could be improved if they were to work on automation related to gathering metrics from more applications without the need for instrumentation and things like that. I'd like them to work more on that.

Additional features they could include would be more automations related to applications and monitoring, user experience monitoring on the application level. Improvement on technical support would also be helpful. 

I've been using the solution for six months. 

This is a stable solution.

I haven't tested the solution for scalability but from the specifications it seems that it would be easily scalable. 

The technical support could be improved - their response time can be quite slow. 

Prior to using Azure Monitor I used SolarWinds. I think that SolarWinds is more infrastructure level oriented while Azure covers infrastructure but also covers the application side. That's why we migrated to Azure.

The initial setup was very straightforward. Transfer to the solution required some training so I think in total it took us about two weeks. 

Before choosing Azure Monitor, we evaluated it compared to SolarWinds and Dynatrace, which was a more expensive solution.

This is a good enough product for anyone wanting something that might not be top of the range but it does the work easily, is simple to configure and is a fair price.  

I would rate this solution an eight out of 10. 

I use the solution to monitor the infrastructure and applications. 

I need connectivity with cost management. 

Azure Monitor's customer service is good. 

Positive

The tool is expensive. 

I rate Azure Monitor a nine out of ten. 

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

The solution's most valuable features are its ability to focus on delivery and maximizing the performance of applications and services.

The solution's monitoring feature has limitations for analyzing multiple metrics. Also, its support services could be better.

We have been a customer of AWS Monitor for less than a year.

It is a stable solution.

We have more than ten people using the solution.

The solution's technical support services need improvement.

The solution's initial setup was straightforward.

The solution is expensive, but it is worth the price.

You can use this technology, as it is unique to Microsoft's services. It focuses on performance monitoring. It is highly effective for diagnostic purposes, viewing metrics, and enabling/disabling logs. It facilitates data gathering and logging, as its name suggests.

I rate it an eight out of ten, as we had a great experience learning the technology.

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

The product is very good for developers who want to integrate with Visual Studio. The solution provides an overview and high-level information on what hurdles to expect, and which endpoints have problems. 

If Azure Monitor wants to compete with other APM products in the industry, it has to stitch together the information and user flow. It also needs to provide all the information, as you get with Stock Trace, including details related to where the call came from and where the problem lies. That's what we'd like to see. With a solution like Dynatrace, you have a clear path and you know which calls were made before and after the problem, and where the issue occurred. That feature is lacking in Azure Monitor.

I've been using this solution for a year. 

The solution is stable. 

The solution scales easily. It's not a big deal for Azure Monitor or any other APM product.

With Azure, implementation needs to be carried out in multiple places and you need to add other things to get the information and that's a tedious process. The Dynatrace setup is much easier. 

We made a comparison between Dynatrace on-prem and Azure Monitor as to what each solution offers. Azure is great for developers wanting to integrate with Visual Studio but when it provides Azure monitoring information on the dashboard there is a lot of Google analytics. When it comes to the application performance monitoring information, Azure gives you the overview or high-level information regarding issues and which endpoints have a problem, but it doesn't give you anything in-depth at the matter level.

It's important to know what your requirements are. If you're able to put best practices in place, and need to add SBKs and turn on profiling at the meter level to look into the details, then Azure Monitor can help. But if that's not something you need, Monitor might not be the best solution for you.

I rate the solution six out of 10. 

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

It has good troubleshooting features like automated troubleshooting. It is also a flexible solution and a low-cost product. It includes all the features that are required for multi-cloud and public cloud.

If it is configured incorrectly, you can end up with a huge bill. Sometimes, a lot of data is collected and stored, and we may get charged for that kind of storage which is an issue.

We have been using this solution for more than two years and are currently using the latest version. It is a cloud-based solution and deployed on public cloud. Our cloud provider is Microsoft Azure.

It's stable and constantly updated with new features and functionalities.

It is scalable and can scale to any size. Five people use this solution in our organization, primarily administrators, DevOps and security personnel. It requires about two to three people for deployment and maintenance. We have dedicated people from the monitoring team that do this. We plan to expand the number of users eventually.

The technical support is quite responsive. Microsoft support is pretty good. I rate the technical support an eight out of ten.

Positive

The initial setup was straightforward and not complex. Deployment took a couple of days, and it was deployed in-house.

We have seen an ROI. It is a helpful tool and provides proactive information about the infrastructure.

We did not evaluate other options. Azure Monitor is one of the most non-native tools from Microsoft, and it's well-integrated.

I rate this solution an eight out of ten. I recommend this solution to others. They should try Azure Monitor to see if it fits their requirements gradually. Additionally, there isn't a lot of upfront investment required to set it up.

The configuration could be improved in the next release because it takes a little time. However, they regularly update their scalability and features.

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.

The most valuable feature is that it's stable. It hasn't crossed any thresholds. 

The troubleshooting logs need improvement. There should be some improvement there. I have a hard time finding the right logs at the right times whenever there is an issue occurring. They should simplify the logs. 

I have been using it for around two years. 

We definitely do have plans to increase the usage but it depends on what the management calls. I'm not the authorized person to make calls here but we do have plans to increase the current infrastructure.

We have a separate team that handles creating incidents with Microsoft.

I would rate Azure Monitor an eight out of ten. In order to make it a perfect ten, the solution should be simplified. For a beginner, it's kind of complex. It should be made easier for beginners or newcomers.

I would recommend this product. We get good results from Microsoft Azure, so that's why we stick with Microsoft Azure. 

I definitely recommend this product to all my colleagues or my friends or my friend's companies.

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. 

They can simplify the overall complexity since you have multiple data sources in the cloud for monitoring. It's quite simple, but there are so many portals. It takes time to work with it. If they could simplify the user configuration, that would be good.

The integration capabilities could use some improvements.

The product is stable.

It's a service from Microsoft, so it will scale.

I have not contacted the technical support for Azure Monitor.

It is easy to create a ticket. The overall Microsoft Azure could be faster.

This was only the traditional basic monitoring for Azure.

It depends of the things that you're going to monitor. For example, when configuring a third-party social Internet application on IaaS services and PaaS, I don't have a software development background. Therefore, it's quite difficult to ask the infrastructure guys, "What is something that I need to monitor from the Azure's SQL Server databases and infrastructure."

It's a fast service to deploy. It's more about defining the configuration. You need to find the right attributes to monitor. It takes about two weeks (10 to 20 days) to assign what to monitor. The actual configuration is quite fast. 

I did a private installation for the customer's Intranet.

We use Azure Data Factory mainly, and we build our own ETR using Databricks. We are a services company, so depending on the requirement for the customer, we use all of Azure's products. We work with infrastructure deployment and want to monitor the health of our deployments.

The metrics and alerts in Azure Monitor allow us to set thresholds on the metrics and receive alerts, providing a good facility for monitoring.

Azure Monitor has metrics and alerts capabilities. It allows you to set thresholds on the metrics and receive alerts. This is an important feature for monitoring.

Azure Monitor could improve by adding capabilities for data observability and integrating more tightly with their data platform components.

I have been familiar with Azure Monitor for the last three to four years.

The technical support by Microsoft Azure is good, however, there is room for improvement in their overall competence.

Neutral

Previously, we used open-source tools before adopting Azure Monitor.

Using Azure Monitor is less of a hassle for existing Azure customers than procuring another product, even if the cost may be slightly higher. Avoiding additional bureaucracy is also easier when using Azure Monitor as part of the existing Azure suite.

I'd rate the solution eight out of ten.