Azure Monitor Reviews

Azure Monitor helps monitor resources to get alerts on the usage or incident's generation. One can also use it to log the events in the event's hub or analyze them through Azure Log Analytics workspace and SIEM tools available to analyze your resource utilization.

The logs, analytics, alerts, and Azure Log Analytics workspace are valuable features in Azure Monitor.

Improvement is a continuous process, and Azure Monitor should keep improving the solution per the evolving trend and technologies. The scalability could be improved as there are some limitations.

I have been using the solution for more than four years.

It is a stable solution. I rate its stability a nine out of ten.

It is a scalable solution but needs some improvement because of its policies.

Azure Monitor is useful at the enterprise level because it already has many resource monitoring solutions.

I rate its scalability an eight out of ten.

Technical support is good and helpful as the services they provide us are based on the SLA we have with them.

The initial setup is easy. Those who opt for Azure Monitor should use it as per needs. For example, one can use it to monitor resources, administrative operations, or log events. The solution was deployed on the cloud.

My company is okay with the current pricing of the solution.

I recommend the product to those planning to use it. I rate the overall product an eight out of ten.

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.

With the solution's help, we can detect database performance issues, like which tables are missing in the indexes on some columns, etc. It helps us monitor timeout in the database, such as performance issues of the queries. If the queries timeout in five minutes, we can analyze the problem with the help of Application Insights. We can detect the problem of a specific step or reason responsible for letting the application fail or crash. For example, if the application crashes during Selenium's end-to-end test on the UI, we can find the reason by going through the logs.

The solution has tons of valuable features.

They should include advanced logging on the database level in the Azure pool. Presently, we are not able to catch the transaction logs. The preview mode is available only for dedicated SQL servers and not for a database pool. They should improve this particular area of the solution. 

They should add a built-in feature for tracing the request and responses. Currently, it does not get measured automatically, and we need to write down the custom solution to check the request and the responses in the logs. They should create a log utility to log the request and send it to the Application Insights in the integration as a custom attribute. 

There should be default parameters and headers, which we can customize. It'll be beneficial because, at present, we only have responses, but not the requests. It is the solution's downside.

We have been using the solution for six years.

I rate the solution's stability as a five for the European region and ten for other regions.

I rate the solution's scalability as a ten.

A part of the setup process was straightforward. At the same time, a part of the process required some guidance because the Azure monitor evolves constantly. Most of the time, the blog post or guidance article on how to set up gets outdated quickly. Sometimes many things don't work as expected or as written in the Microsoft documentation.

If you have a solution built on Microsoft technology, go for Azure Monitor. I rate it as a nine out of ten.

We use this solution for recording the logs and generating dashboards using Azure broad view insights. It is a great solution.

The solution should have cross-connection or cross-communication between tech partners. For example, it should be able to read the logs in the database and GCP environment by enabling a couple of hooks to collect information from cloud vendors to Azure Insights.

We have been using this solution for two years.

It is a stable solution. 

Azure Monitor is scalable, and we have not encountered any issues.

We have used Microsoft support for one or two usages regarding our area integrations. We already have some education with Microsoft Azure, and I believe a couple of engineers from Microsoft work on the technical support.

It is a move-in powerful feature compared to other market-leading tools. It has the capability to not only monitor your applications but also deliver dashboards. We can pinpoint different areas for improvement and it provides the ability to identify precisely what dash metrics are failing. It is introspective on contextual logging and delivers good dashboards. This helps senior management manage, alert, debug and look at operational insights.

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. 

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