Azure Monitor Reviews

I have used the cloud version of Azure Monitor. If customers actively use a bunch of servers or resources and need to monitor the metrics of those devices or resources. Azure Monitor is used in such aforementioned cases for monitoring.

For instance, if a resource has been changed or access has been granted to a specific resource, a certain hard disk is offline, or a critical amount of disc space is in use, an alert needs to be generated and forwarded to the concerned professional, who is meant to work on resolving the alerts. 

Suppose a CPU is running at 100% capacity for a long duration. In that case, a service desk professional or a system administrator needs to be alerted using Azure Monitor to take appropriate action. 

The features that are most valuable are the alerting function and the logging functionality to analyze certain issues using log analytics or queries. The solution also supports deployment towards a set of resources based on data collection rules. 

The onboarding process of certain assets and the overall UI can be improved in Azure Monitor. 

The solution should allow the addition of certain assets to the monitoring process so that they can be incorporated into the existing monitoring set. The aforementioned process is possible using data collection rules, but it might also be possible to use agents or a network scan to find resources that can be implemented. 

I have been using Azure Monitor for one and a half years. 

I would rate the stability a ten out of ten. 

I would rate the scalability an eight out of ten. The solution can offer impressive scalability because there aren't any limits in terms of tiers that need to be adhered to. Resource addition to Azure Monitor can be carried out in a straightforward manner. The cost of the solution escalates with the proportion of data ingestion, but it's quite logical. There are between 100 to 200 users of Azure Monitor in our organization. The usage of the solution varies day to day in our company. 

I would recommend others to use the solution and to keep it updated, but presently, in our company, we don't have plans to increase the usage of Azure Monitor. 

In our company, we previously used PRTG Monitor which had similar capabilities to Azure Monitor. Our company decided to switch to Azure Monitor because they were willing to deal with solutions from a single vendor. As our company expanded, they needed a vendor as a partner who had solutions suitable for large-scale companies and their internal base units. 

I would rate the initial setup as seven out of ten. The tool's configuration and usage are highly intuitive. The maintenance of the solution is majorly handled by the vendor in our company, but we still remain responsible for the data collection rules and alerts.

Our company team also remains in charge of actively incorporating the correct resources that need to be monitored by the customer team from the vendor. In our company, a team of eleven professionals remain involved in the maintenance process. 

When the solution's monitoring feature is implemented, you can guarantee the continuity of your company's IT environment and prevent data outages. Due to the high availability of your company's services, you can achieve a high ROI with Azure Monitor. 

I would rate the pricing an eight out of ten. Besides standard licensing fees the customer needs to additionally pay based on the ingested data size. The settings of the solution can be tailored during purchase based on the size of data collection and monitoring, but the cost of the solution will also increase with the data size. 

For infrastructure monitoring in our company, the alerting feature has been the most beneficial as it notifies on time to manage certain actions. Azure Monitor has impressive integration capabilities. It's not only a complete infrastructure in terms of certain resources residing in the Azure tenant; edge resources can monitor certain assets that are not in the cloud but are on-premises.  

Some time ago, our company had high CPU usage, and it was across Azure Virtual Desktops, we used certain metrics to view how many resources were in use and what was the cause of it. Then, based on the overview of the aforementioned step our company team decided to upscale some services so that the resources were more evenly divided and spread out.

Following the aforementioned initiative, the complaints regarding performance issues were eradicated. Based on the input or reports from Azure Monitor, our company team could make a decision, which in turn led to performance enhancement for end users. I would overall rate the product an eight out of ten. 

My advice to others would be to decide upfront which resources you would prefer to add to your monitoring, which is crucial for your organization, and what aspects you need to have Azure Monitor for. Due to the aforementioned initiative, you can start with the most essential features of Azure Monitor, and then you can add upon the original set later on to extend the monitoring capabilities. 

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

Log analytics and log queries are the most valuable features of Azure Monitor.

We encounter some difficulties in monitoring the operating system on its own. Therefore, we require additional tools to obtain a comprehensive view of the entire application chain.

The technical support can be faster and has room for improvement.

The dashboarding and reports could benefit from improvements, as Microsoft seems to prioritize Power BI as their main dashboarding tool. Perhaps these enhancements could be integrated natively into Azure, as there is certainly room for improvement in that area.

I have been using the solution for seven years.

I give the stability a ten out of ten.

Azure Monitor is scalable.

The technical support is not always perfect. Sometimes it takes a long time to get the right person who actually understands the issue to work on the case.

We find the initial setup to be straightforward as we have extensive experience in it. However, configuring Azure Monitor may prove to be complex for those who are less experienced. The deployment takes about 30 minutes. The deployment process is using a CICD workflow that is fully automated.

The implementation was completed in-house. I work as an integrator and am responsible for implementing solutions for our customers.

There is a monthly fee for the alerts triggered and the data stored.

I give the solution an eight out of ten.

We have 35 customers using the solution.

We have a small DevOps team of about ten developers that maintain this life cycle.

The reason for using this solution is to align with the hyperscaler's capabilities as close as possible, and this is the best-integrated solution we can find.

As a Microsoft MVP and MCT, I help our company's clients use Azure Monitor in different ways depending on what types of activity they want to monitor. From a big picture perspective, this entails checking and testing both the performance and efficiency of cloud-based applications.

Starting from the basics, such as when monitoring VMs, you are able to integrate Azure Monitor with the virtual machine so as to create alerts and notifications that are automatically triggered when, for example, the machine's performance rises above 60-70%.

You can also use Azure Monitor to help you understand the total internal activity, including the CPU or RAM performance, of specific applications on the cloud. And beyond that, there are many other metrics detailing which users have logged in (or are concurrently logged in) to the application or VM, while showing the ratios of their activity in total.

For me, the best feature is the log analysis with Azure Monitor's Log Analytics. Without being able to analyze the logs of all the activities that affect the performance of a machine, your monitoring effectiveness will be severely limited.

Although it's not always the case, the price can sometimes get expensive. This depends on a number of factors, such as how many services you are trying to integrate with Azure Monitor and how much storage they're consuming each month (for example, how large are the log files?).

Of course, this totally depends on the particular customer's environment. As the implementer, we can typically only advise on the technical outcomes for a certain usage scenario of Azure Monitor, and not necessarily the advantages or disadvantages of paying for Azure Monitor in their particular use case. For example, if they are paying $400 per month, the advantages for the customer might be that they reduce technical headaches in ensuring proper service performance without having to invest in a separate IT member to handle the monitoring. And for many customers, this makes good business sense, which is why when we propose the use of Azure Monitor in such a way and give them an example, they often take us up on the proposal, despite the costs involved.

I have been using Azure Monitor for five years.

Azure Monitor is definitely a stable product once we have deployed it to our target. Azure Monitor, when deployed to a VM, will give you a stable interface for taking readings on various aspects of a machine's performance, such as what's going on with the CPU, memory, and data communications.

When it comes to more advanced usage with deeper monitoring, Azure Monitor can integrate with AI to make the process of advising what to do about resolving certain problems much easier.

Azure Monitor is a key part of service integration and it is easy to scale and extend as needed. You can also integrate other services, even third-party ones, with it.

It provides options for scaling it to your own needs in various ways, such as by providing a choice of what types of logs will be generated and how many days you would like to keep the logs for. It also provides options for how many servers you would like to monitor, and whether you will be logging on an hourly, per-minute, or per-second basis.

I am largely satisfied with how the technical support from Microsoft explains their solutions to the issues that we've raised. Although, most of the time, they simply share the most current link from their blog of knowledge base that explains the specific activity that must be done to resolve a problem. This is because Microsoft engineers don't actually provide the technical work themselves, but instead act as advisors, where companies like mine will then be the implementer of the suggested solutions.

The setup for Azure Monitor itself is easy to understand and, for generating logs and such, it's a simple process of configuring how you would like to gather your logs and for how long you would like to keep those records, etc.

It won't take anyone that much time to deploy their monitoring system with Azure Monitor. This is especially true if you understand your business needs well, because you can then quickly integrate Azure Monitor (and Log Analytics or Workbooks) inside your application as appropriate. As an estimate, it could take up to three or four hours at most.

We implement Azure Monitor in-house. Our deployment plan is to first obtain the Azure identity and then make an effort to better understand the service that will be running on the Azure cloud. For example, is it IaaS or PaaS? If it is based on PaaS, then we'll go straight to the application inside the PaaS, and if it's on a VM, then we'll go to the VM (or container) instance and set up the deployment from there. Here, the deployment also depends on the specific resources or Azure subscriptions in use.

Customers of Azure Monitor must pay an amount that depends largely on how many services they need to integrate and the storage space required in terms of logs, etc. If they only have a few small services to monitor, the price won't be too high, but on the opposite side of the spectrum, it can certainly get pricey.

Fortunately, customers can use the calculator provided by Azure to easily estimate the total monthly costs based on the customer's requirements. 

Along with Azure, I also have experience with New Relic, for which I have handled both deployment and connectivity.

I can definitely recommend Azure Monitor for most people, but before recommending it to all I would caution that whether you choose to use it depends largely on the type of service that you are running on the cloud.

One must first be clear about the outcomes of the service that is to be monitored; if it is a critical service or application where you absolutely must monitor each data point or watch for incidents, then you will certainly want to use Azure Monitor.

On the other hand, some companies are running services on the cloud that are not actually critical in the grand scheme of their operations, and to these companies I would not blindly encourage using Azure Monitor. Of course, if they are interested nevertheless, then I would say, sure, they can go forward with it as long as they understand that they will have to pay Microsoft accordingly in order to get something out of Azure Monitor. 

I would rate Azure Monitor an eight out of ten.

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.

The most valuable feature is the universality of their functionalities in all Azure services, including, software solutions.

I would like more transparency when we use the solution with another environment, like on-premises, or on another cloud environment, like AWS or GCP.

What I would like to see in the next release is not directly related to the solution, but it depends on Azure cost management. Maybe if we had the opportunity to monitor the cost of Azure and another cloud in one environment, and maybe integrate that with Azure Monitor, that would be incredible and amazing for any IT company to offer that to our customers.

I have been using the solution for almost four years.

The licensing is a monthly fee.

I give this solution a nine out of ten.

I am monitoring all of my Azure Monitor and getting good reports. I can customize the reports to get the information I need. I am also getting emails about which AAS instances are down and everything in the system related to my services.

It is easy to use, scalable, and user-friendly. Microsoft has Many guides and videos to help you understand how to create and use Azure Monitor.

I have used multiple products like Webex and PRTG. Some features could be added. Azure Monitor should add SMS and APIs. We have very limited access to Azure Monitor. I usually get alerts on my phone when they are integrated with Slack.
I am not always available, but my team is. Sometimes, I am traveling and don't have access to my email, but I have Slack and other third-party projects that send me instant messages if a sensor goes down.

I have been using Azure Monitor as a customer for seven years. I have been working in my current company for the past year, but in my previous organization, we used Citrix and Azure Monitor to monitor the instances. 

The product is scalable.

We have almost 23 users, and the network security zone has four users using the solution. Currently, we are not planning to add usage.

The technical support team is good. Sometimes, there was a long waiting period. I've never faced any issues with Azure Monitor. If I’m deploying, I’m drafting a mail to the Microsoft team and receive the response after three days of purpose.

Positive

I faced many issues in my previous organization since I was a beginner in Azure, but I have no issues now. When implementing Citrix on-premises to Azure, we had some problems with adding sensors and SSL certificates.

If I have experience with Azure monitor, everything will come into word-of-mouth publishing. If I am satisfied with Azure monitoring, I will tell my colleagues in any previous organizations or anyone I’m connected with on LinkedIn.

Overall, I rate the solution a nine out of ten.

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

Azure Monitor provides visibility and proactive alerts, which means that if anything happens, I get automated alerts from the performance monitoring tool and can fix the problem.

Azure Monitor's best features are its graphs and charts, the different visibility options, and reporting.

Azure Monitor's integration with applications could be improved. There is limited support in terms of what it can monitor, and the connectors are built in a way that only monitors a specific area. In the next release, Azure Monitor should improve its visibility features, especially for WordPress websites.

I've been using Azure Monitor for over a year.

Azure Monitor is very stable - I'd rate its stability ten out of ten.

Azure Monitor is very scalable - I'd rate its scalability ten out of ten.

Microsoft's technical support is ok, but its response time is quite high, and you have to buy very expensive support to get a better response time.

Neutral

I previously worked with SolarWinds and ManageEngine, but both were developed for on-premise environments.

The initial setup was straightforward, and deployment took around thirty minutes. I would rate the process nine out of ten.

I implemented Azure Monitor myself.

Given its low price, Azure Monitor gives good ROI.

Azure Monitor's price is minimal to the point of being almost negligible. I would rate its pricing eight out of ten.

Azure Monitor is simple and cost-effective, but make sure that it can provide you with the information you're looking for, the right metrics, and what you need in advanced and application monitoring. I would give Azure Monitor a rating of seven out of ten.

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.

The detailed logging is great. Detailed logging is the most impressive part. Also, we are observing our cost on the live environment. We know what kind of budget is required. 

Also, we are getting all the problematic area details, so we can arrange ourselves according to the application development part. 

The alert parts are great. It's crucial for our site, just getting the alerts on time.

It's easy to set up.

It is a robust, stable product.

The solution scales well. 

We are sometimes confused about the details. We would like to have a flow in terms of how a new application should engage with Azure Monitor. We must understand: what is the most crucial part of our monitoring or support? We are not very good at it yet. 

Currently, it seems it's complicated to get the correct information in terms of what to do and how things work. Maybe it would help if they offered some guidance or written guides. For example, we say that project manager should follow their quality issues before putting the application into production. It's so complicated from their side for the project managers. Some kind of simplification is required for people engaged in the platform. 

Still, it's very new, and we will be gaining experience, and we may see much more substantial things in the future as we uncover more capabilities.

We've newly engaged with the product. We've only used it for a few months at this point. 

The solution is very stable. It's robust. The performance is excellent. There are no bugs or glitches and it doesn't crash or freeze. The reliability is high. 

We'll continue with Azure Monitor.

It is a scalable solution. It's not a problem if you need to expand it. It reaches about 200 users right now. 

We do have access support and get it when we need it. We are satisfied. They are okay. 

We've also used New Relic. We moved away due to the cost. 

The solution is straightforward and very simple. It's not complex at all. We're effortlessly engaging with it. We implemented ten applications in one week.

Only two people are needed for deployment and maintenance. They are admins. 

We did not need to get the help of consultants or integrators. We handled the setup ourselves in-house. 

The licenses require a subscription based on the log file sizing.

The pricing is better than, for example, New Relic. New Relic was too costly for us. 

Based on what we see right now, I'd rate the solution eight out of ten. Maybe, as we use it more, we will rate it higher in the future. Currently, we are very new to using this product. 

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.

Azure Monitor has helped our organization to have insights into issues and informs us before an issue becomes a very critical stage. It provides us a baseline on how to prevent serious issues in the future. You don't want it to get to 90 percent usage, if you catch it at 70 percent, it helps preserve the lifespan of that sever or allow your services to keep running efficiently or effectively. It keeps the availability of whatever service that you're running on that server, is in check. This is one of the most important parts of the service.

Azure Monitor is useful because of the useful application insights and telemetry, such as metrics and logs.

Azure Monitor could improve the visualization aspect and integrate better with other third-party services.

I have been using Azure Monitor for approximately four years.

Azure Monitor is a stable solution.

The scalability of Azure Monitor is very good because it is on a public platform.

We have approximately 500 users using this solution. We are extensively using Azure Monitor and we are always adding to it.

The support we have received from Microsoft has been good. Depending on the issue you might be facing, they could respond within less than 24 hours during business hours.

The initial setup of Azure Monitor is straightforward. The process took us approximately one hour.

We did the implementation of Azure Monitor in-house.

The price of the solution is reasonable. 

I have evaluated Datadog before choosing Azure Monitor.

I rate Azure Monitor an eight out of ten.