What is our primary use case?
We are using Azure Network Watcher to monitor logs or conditions in the cloud services.
The main purpose is to monitor the logs. Once the services are deployed to the cloud, we will primarily check for any log failures or diagnose any issues with the services we have implemented. Additionally, we will enable logs for virtual networks, specifically for virtual machines where we create the services. By enabling these logs, we will be able to closely monitor for any log failures.
What is most valuable?
The most valuable feature of Azure Network Watcher is using the gateways with the connections. The monitoring is useful for the logs and application insights into the data. The traffic filtering issues when it comes to deploying those applications are helpful.
Azure Network Watcher allows for the isolation of network segments, where you can apply filters to the logs. This allows for more organized monitoring of the networks and the ability to deploy firewalls. It also includes features such as connection and time limits for monitoring, as well as the ability to create a dedicated virtual machine network for logs. This allows for more efficient monitoring and the ability to avoid connection limits and set specific times for monitoring client requests.
What needs improvement?
The solution could improve by limiting the need to clarify the logs. When the clarification is minimized, it is better for everyone involved.
In a future release, it would be helpful to have a monitoring tool that can have
a pictorial representation of all the logs. This way people can understand exactly what the issues are visually.
For how long have I used the solution?
I have been using Azure Network Watcher for approximately four years.
What do I think about the stability of the solution?
When it comes to the stability of Azure Network Watcher, other monitoring tools have high availability, and Azure Network Watcher allows for maintaining stability as well. I use Splunk and other tools for monitoring. This is because, while Azure Network Watcher is mainly for monitoring Azure services, Splunk is more comprehensive and can be used for monitoring things outside of Azure as well. In terms of stability, the initial setup may take some time, but overall Azure Network Watcher is a good option when compared to other monitoring tools in terms of stability, scalability, and reliability.
I rate the stability of Azure Network Watcher eight out of ten.
What do I think about the scalability of the solution?
As a DevOps Azure cloud service provider, our team consists of seven to eight people. Currently, I am working with Capgemini America on a project for State Farm. Our team is divided into smaller teams, each working on a specific product such as home insurance, auto insurance, and fire insurance. While each team works independently on their respective products, we do not combine efforts for a single team project.
In order to ensure high scalability, we use Kubernetes for scaling. Kubernetes has been effective in maintaining high scalability and preventing any issues with client technology. There may be times when services become low, and in those cases, we need to work harder to increase the Kubernetes ports to achieve high scalability.
During times of high usages, such as during the COVID pandemic, it becomes important to closely monitor logs to address any issues that may arise. In these situations, client-side issues such as crashes may occur and it becomes necessary to quickly increase the number of ports and maintain scalability. This can be a time-consuming process and may cause disruptions if not addressed promptly.
I rate the scalability of Azure Network Watcher an eight out of ten.
How are customer service and support?
I do receive support from them Azure Network Watcher. At times, I have difficulty and I am not proficient in all areas. During those times, if there is an urgent requirement from a client or a need to submit a set of logs, I seek technical support. Even now, I may encounter trouble and seek assistance from others.
There are complexities involved in using the solution, I find it challenging to complete the task within the given timeframe. During those times, I seek assistance from my team and technical support to help me overcome these difficulties. I often turn to team members who have more experience and a strong understanding of Azure Network Watcher for guidance and support. This has been helpful in addressing the challenges I face.
I rate the support from Azure Network Watcher an eight out of ten.
How would you rate customer service and support?
How was the initial setup?
The initial setup involves navigating and signing into the portal and creating the necessary resources for the Azure Network Watcher. This process of creating the resource may take more time initially, but once it is set up, it will be easy to manage incoming services. This will involve creating a virtual network and a separate resource group.
I rate the initial setup of Azure Network Watcher an eight out of ten.
What other advice do I have?
I would advise others Azure Network Watcher is a useful tool for monitoring virtual machines, application gateways, load balancers, and networks. It provides advanced and precise monitoring of clients or jobs. It's a good tool for monitoring, but there are other ways to monitor. Specifically, when compared to other monitoring tools, Azure Network Watcher is better in terms of stability and availability for our use case. It is a reliable monitoring tool.
I rate Azure Network Watcher a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.