Azure Monitor Reviews

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.

The most valuable features of Azure Monitor are the login analytics workspace and we can write any kind of custom queries in order to receive the data that is inserted into the login analytics workspace, diagnostic settings, et cetera.

Azure Monitor could improve network performance monitoring and make it more advanced.

I have been using Azure Monitor for more than two years.

I would rate the scalability of Azure Monitor a six out of ten.

It might be a case that there are certain services that are not available in other regions, but it's available in certain regions. You can face certain issues in one place and not another. You can't implement the same solution in all the regions. However, it might be a limitation of the cloud provider.

Technical support is good. In terms of supportability, Microsoft gives a good level of support if the company has a business account and an enterprise level of support. I believe that could be sufficient.

The initial setup of Azure Monitor was in the middle range of difficulty.

We did the implementation of this solution. We have automated everything using the infrastructure or provisioned.

There is a team required for the maintenance and support of the solution.

The cost of Azure Monitor application performance should be less expensive.

My advice would be if you can maintain the configurations that you have done, and if you have automated it, then Azure Monitor would be the best solution. The support is anyways good, but if you do not want to maintain the overhead of operations, then it should be outsourced.

I rate Azure Monitor a seven out of ten.

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. 

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

The feature that I found most valuable in Azure Monitor is its monitoring abilities. With Azure Monitor, you are able to monitor all of your cloud resources across multiple subscriptions in one dashboard and create solution-specific alerts that can trigger an email to the team responsible for that specific solution.

The ability to customize is endless. The majority of the data used for creating alerts does not require any agent installed, like so many other monitoring tools.

Azure Monitor is a monitoring solution that you should not miss out on the second you move workflows, solutions, infrastructure, and much more onto the cloud.

Azure Monitor is a complex product because you can use it to monitor different things, and that could be an area for improvement. Having templates by Microsoft added to it is another area for improvement.

What I'd like to be added in the next release of Azure Monitor is an overview of best practices from Microsoft and what they'd recommend users to monitor.

Assigning an alert is another feature I'd like to see in the next release of the solution. Currently, you can't assign an alert to anyone, if a server crashed and you need to assign that alert to a specific team, it's not possible.

Azure Monitor is a stable solution.

Azure Monitor is a scalable solution.

The initial setup for Azure Monitor is quite complex. If I would rate its setup from one to five, with one being complex and five being straightforward, I would rate it 1.5.

Azure Monitor is not too expensive. On a scale of one to five, with one being expensive and five being affordable and competitively priced, I'm giving the solution a four.

I have not used the technical support for Azure Monitor.

Azure Monitor relies more on your ability to collect data and make the correct queries, while on-premises solutions rely on an agent and have many templates to choose from.

Azure Monitor is a nice monitoring tool, particularly if you have the skills. I'm rating it nine out of ten, I can't give it a ten because there's still something missing in it.

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 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 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 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.

The only things for which our company might be using it are storage monitoring and performance monitoring. Nothing else.

In the last company where I worked about a year ago, it looked very simple. 

Its interface has room for improvement. Some of the options or some of the ways to navigate could be improved, but that's a general thing. All companies are always modifying the user interface because there's a better way to move things around or a better way to put things so that people can see the product features that they didn't know existed. For me, that's probably the biggest thing.

It's a little lacking in features. There are some things that they could do to improve it, but it's not that big of a deal for me. There's obviously competition that does a lot more, but for what we're going to be using it for, it's perfectly fine. The biggest one is probably just the user interface. There could be more advanced logging at the database level. They can also improve their query builder to allow you to search for things better, but I last used it about a year ago. They might have already changed a ton of things in the newer versions.

I've used this solution for two years. I last used it in my previous company about a year ago.

It was pretty straightforward. 

Based on my experience with Azure Monitor about a year ago, I'd rate it a seven out of ten. There are better tools with better interfaces, deeper integration into applications, and things like that, but they could have improved it, and it could be a lot more comfortable now than when I was using it.