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.
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.
It's a Microsoft native tool, so it works well with other Microsoft technologies, which is predominantly what our customer end-user base is.
Automation is a key benefit of it as well. You can link one box to automatically resolve the issues off the back of another. There's quite a lot you can do with it.
The query builder could be better. In comparison to other monitoring tools, in order to use Azure Monitor, your engineers need to have KQL experience. If they don't, it's not intuitive as a system. They need to understand KQL and get the right queries to get the value that they want, whereas a lot of out-of-the-box solutions, such as FrameFlow and Datadog, can be given to somebody untrained, and the UI will guide them through what they need to do. You lose some customization with that, but you don't need to train people on it. It would be good if Microsoft had some form of query builder in place so that you can choose a metric and it writes the code for you. Some kind of AI elements would help with that skill gap for organizations.
Their support also needs to be improved. I've had a lot of issues with their support.
I've been using this solution for two years.
I've not had any issues with it so far. I'd rate it a ten out of ten in terms of stability.
You can scale it pretty easily. I'd rate it a nine out of ten in terms of scalability.
We probably have about 30 people using this solution.
Their support is not great. We pay for Premier Support because we're a partner, and even that's pretty bad. I've had a lot of issues with their support. It has nothing to do with Microsoft Azure Monitor as a tool. I'd rate Microsoft's support for any of their systems at the absolute lowest number that I possibly can because it's pretty bad. The time to get engineers is an issue, and their skills and knowledge are also questionable. My team is more knowledgeable than them on some of the platform-related things.
They also make a lot of mistakes. They have brought the platform down a couple of times in recent months. There has been a whole heap of stuff. I've had quite lengthy conversations with our account manager about how poor the service is, and there isn't anything they're going to do about it because it's at the organizational level. It's not one team. It seems Microsoft is going through some struggles at the moment.
Negative
We used FrameFlow. We switched to being native. It's a Microsoft native tool.
The deployment duration depends on the use case. It depends on what you want. You don't deploy Azure Monitor itself. It's not like other tools where you have to install nodes and install the software and deploy it. It comes natively with Azure as a platform, so the implementation time is just dependent on what the client wants out of it. For our use case, we set up a template of about 15 to 20 key metrics that we monitor, which probably doesn't take longer than a day to deploy. It's all templated. We just run a bunch of CLI commands, and it deploys those templates, but if you have a customer who wants to start monitoring more intricate or complex things such as SQL databases and applications, you can probably spend months on it.
In terms of the number of people required, one person can do it if he or she has the skills for it.
I don't really measure return on investment. It's about visibility. It's about providing the service for us. If we compare the implementation versus the visibility we get, we do get a return. It doesn't take that long to deploy, but it can subsequently create a lot of visibility. So, its return on investment is probably okay.
Its cost depends on the ingestion of the logs. It could go anywhere. For an out-of-the-box platform such as FrameFlow, you pay pretty much a fixed price and you get what you get, whereas, with something like Azure Monitor, you pay by the ingestion charge, so you can have one client who pays hardly anything for the same alerts, and another client pays loads and loads. From experience, Azure itself isn't a cheap system. It's not a cheap tool at all. If you don't configure it correctly, it's really expensive. I'd rate it a nine out of ten.
I'd advise learning KQL before you think about it. If you know KQL, you can do a lot with it. If you understand KQL, then it's really powerful, and you can do a lot with it. If you don't understand it, you should probably steer away from it because you won't be able to do much. You won't get much value out of it.
I'd rate Azure Monitor a seven out of ten.
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.
We like the monitoring. We can look for the downtimes and look at the log to see whenever there is a crash and all the information around it.
It's very straightforward to set up.
The solution is stable.
You can scale the product.
The pricing is less than Dynatrace.
They need to work with other cloud providers - not just Azure. We'd like them to work with clouds such as GCP, AWS, and Alibaba, for example.
I've used the solution for quite a long while, however, recently we moved from on-premise to the cloud.
It's quite stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.
The solution is scalable.
I've never used technical support. I can't speak to how helpful or responsive they would be.
We are moving our applications to Azure Web Apps.
Earlier we used Dynatrace, however, it was quite costly.
The solution is very straightforward. It's very easy to implement.
We can use different services by Azure, such as virtual machines or Web Apps. These are all quite frequently deployed and it's not difficult.
We handle the initial setup in-house.
I'm not concerned about the pricing. Actually that is handled by a different team.
It is a pay-as-you-go service. We pay as needed.
I'm not sure which version of the solution we're using. A centralized team handles that aspect.
I'd recommend the solution to others.
I'd rate the product eight out of ten.
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.
Azure Monitor is a very easy-to-use product in the cloud environment.
We cannot use AI services with the solution.
I have been using Azure Monitor for five years.
Azure Monitor is a very stable product, and I don't find any bugs in it.
Around 50,000 users are using the solution in our organization.
I have contacted the technical support team regarding how to use the solution, how to monitor, and what to do if we lose any logs. I am happy with the technical support team and the information they provided.
The solution’s pricing depends on how much logs it collects.
The solution is deployed on the cloud in our organization.
Most of the resources are inbuilt monitoring systems. Apart from those things, we can have more monitoring by using the analytics tools. Azure will provide the insights and analytics tool to collect data from all the resources, and we can store it in one centralized storage account.
We can analyze and do a lot of research on the logs. Azure will provide all these things, and it is a very easy-to-use product. Azure Monitor is not a standalone product. An inbuilt agent will be already running when you create any VM or machine. On top of that, we can see the logs as soon as the VM or machine is created.
The solution's documentation is very easy to understand. We can go through the documentation, and we can find the related information very quickly. Azure Monitor is very easy to use.
Overall, I rate the solution an eight out of ten.
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.
One standout feature is its user-friendly dashboard. It simplifies the process of monitoring by providing a comprehensive overview of metrics, particularly in terms of resource utilization. The dashboard allows us to easily track various metrics and quickly understand the overall health of our system.
Establishing a threshold for resource utilization below 40% over a specified duration could trigger an automated scaling down, and vice versa. This way, the system could dynamically adjust configurations based on predefined conditions, such as scaling up or turning off resources. Enhancing and reaching a level of detail that facilitates pinpointing and addressing issues at such a refined level within the application and database components would be helpful.
We have been using it for one year.
We currently find it stable since our present requirements are relatively straightforward, and we are utilizing its basic functionalities.
The scalability is highly commendable with around three hundred users currently using it within our organization. The application we are employing primarily caters to the education sector. It is currently in use by the Ministry of Education, in conjunction with their division offices, and the plan is to extend its usage to the school level. Upon full implementation, we anticipate the user base to grow significantly, reaching an estimated range of twenty to thirty thousand users.
We have utilized Microsoft's Azure technical support services, both from the global cloud support and the local support team in the Philippines. Most of our technical support requests to Microsoft Azure have revolved around resource allocation issues. Initially, we deployed services across different regions, but we later consolidated in the Asian region. However, due to limited space in the Asian region, Azure imposes restrictions on certain resources.
We used New Relic. While Azure Monitor covers resource aspects, New Relic excels in providing a thorough examination of application issues. New Relic can precisely identify problems related to resource allocation, pinpointing issues within the application, whether they originate from application resources or the database.
The initial setup is straightforward.
We operate as a collaborative effort, partnering with Microsoft's education group, which supports the Ministry of Education. Under our agreement, we have an Azure expert within our team whom we can approach for support and assistance in implementation and deployment.
Since we are using the basic set, it is more cost-effective compared to other third-party APM solutions.
It is a more seamless and effective monitoring solution compared to third-party options like New Relic. The alignment of Azure Monitor with our Azure-based infrastructure simplifies the monitoring process, ensuring all applications and resources are easily accessible within the Azure ecosystem. While third-party APM solutions, such as New Relic or NetNix, are useful for troubleshooting specific issues, they face limitations when applied to Azure app services. These services often have restrictions and prerequisites that impede the full utilization of third-party APM for cloud monitoring, especially with the latest Azure technologies. Given these considerations, our recommendation is twofold. For those utilizing the latest Azure technologies, Azure Monitor is advised due to its seamless integration. If choosing a third-party APM provider, it's essential to confirm compatibility with the latest Azure technologies to ensure effective monitoring without encountering potential issues. Overall, I would rate it 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.
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.
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.
We use Azure Monitor to monitor all the infrastructure that we have in the cloud.
Azure Monitor gives us the observability to check everything that we have in the cloud. We can set up some alarms to better manage what we have in the cloud.
Azure Monitor has a direct connection with the infrastructure in the cloud. It's like a built-in feature in public services.
It's really complex to retrieve or query the logs in Azure Monitor. They have another query language, and it's messy. It never works the first time. You have to check a little bit of queries. It's really hard to make queries in Azure Monitor.
I have been using Azure Monitor for five years.
We never had issues with the solution's stability. I rate Azure Monitor a nine out of ten for stability.
I rate Azure Monitor a nine out of ten for scalability. It's a cloud service, and we don't have any issues with it.
Azure Monitor's technical support overall is not perfect.
Neutral
We have seen a return on investment with Azure Monitor because it's a tool that's out of the box in the cloud.
Azure Monitor's pricing is tied to the services. The Azure Insight is a little bit expensive. It's a little expensive if you want to avail all the features.
I am using the on-cloud version of Azure Monitor.
If they are using the cloud, users can use Azure Monitor as the first tool because it already has integration with all the services. However, the query language that I use is really complex. So if users haven't built queries before, they will have several issues with it.
Even for technical people, they will have issues if they don't have experience using a query language. So if they are using Azure, they should use Azure Monitor initially. Later, they can improve the monitoring environment by applying some other tools.
Overall, I rate Azure Monitor a seven out of ten.