No more typing reviews! Try our Samantha, our new voice AI agent.

Azure Network Watcher vs InfluxDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 10, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Azure Network Watcher
Ranking in Network Monitoring Software
42nd
Average Rating
8.0
Reviews Sentiment
5.9
Number of Reviews
13
Ranking in other categories
No ranking in other categories
InfluxDB
Ranking in Network Monitoring Software
13th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), IT Infrastructure Monitoring (14th), NoSQL Databases (6th)
 

Mindshare comparison

As of May 2026, in the Network Monitoring Software category, the mindshare of Azure Network Watcher is 0.5%, up from 0.4% compared to the previous year. The mindshare of InfluxDB is 0.5%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
InfluxDB0.5%
Azure Network Watcher0.5%
Other99.0%
Network Monitoring Software
 

Featured Reviews

Bijoyendra Roychowdhury - PeerSpot reviewer
Program Manager at a consultancy with 10,001+ employees
Network monitoring provides comprehensive analytics while the interface requires further development
The quality of Azure Network Watcher is quite good in terms of the in-depth analysis you can create from these matrices. There are other monitoring tools such as New Relic, AppDynamics, and Dynatrace which provide very detailed network tracing. Cloud providers such as Azure or AWS do not have that kind of GUI-based capability at this point, but using PowerShell or Python, you can develop it yourself. From the GUI perspective, it still needs to evolve in terms of quality and standard, though overall, it is quite good for troubleshooting. Regarding areas for improvement, when comparing to other network tools beyond Azure Monitor or Azure Network Watcher, those tools can identify single failed packets. This level of granularity is not currently possible with cloud providers as they only go to a certain level rather than the granular level needed for deep troubleshooting, though they do provide hints with available matrices.
Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"What I like most about Azure Network Watcher is that it's focused more on the architecture. I also like that it has a packet capture feature that tells you how the packet travels and whether it's exiting Azure, etc."
"This will help the company or the administrator, by helping them see how the traffic moves, to make sure that no entities are having any communication issues or different endpoints with task issues."
"The stability is very good. I rate it a ten out of ten."
"I like the visibility."
"The most valuable features I have found are typology, visualization, and capture."
"The solution is good for monitoring device behavior."
"This is a stable system providing stable performance."
"My advice to others looking into using Azure Network Watcher is to go for it, as you'll have the tool by default when you're subscribed to Azure VNet."
"InfluxDB has played a key role in enhancing system reliability and supporting our goal of delivering a seamless, high-quality product."
"Because of reduced downtime, we benefit greatly from receiving alerts in advance."
"The solution is very powerful."
"Overall, InfluxDB delivered excellent performance, stability, and simplicity for telemetry-driven use cases."
"In our case, it started with a necessity to fill the gap that we had in monitoring. We had very reactive monitoring without trend analysis and without some advanced features. We were able to implement them by using a time series database. We are able to have all the data from applications, logs, and systems, and we can use a simple query language to correlate all the data and make things happen, especially with monitoring. We could more proactively monitor our systems and our players' trends."
"InfluxDB reduced my time to show data without any interruption, also reducing the number of people needed to manage the project; it is very good to have InfluxDB in my project."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"InfluxDB positively impacts my organization because I have optimized my database storage, and by using powerful queries, I am able to find my data logs efficiently and also manage logging."
 

Cons

"It's not the most friendly or straightforward to set up. I don't see the value versus the way you have to set it up at first."
"The solution could use some additional components of the network culture, not only VMs. I'd like to see some additional security features because what they currently have concentrates only on the network."
"The initial setup and deployment could be improved to be simplified."
"Sometimes, you encounter a VPN tunnel, network, or routing issue, but finding out more about the blockage is challenging."
"Azure Network Watcher could improve by having other built-in applications. For example, an application to log activities for in and outbound traffic."
"Azure is good, however, the Fortinet GUI is more intuitive and I like it more than anything else."
"User experience could be improved."
"There are some occasional downtimes, but these were based on Azure-specific issues."
"The error logging capability can be improved because the logs are not very informative."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"I chose an 8 out of 10 because there is room for improvement, such as regarding backups and enhanced security through other types of authentication or encrypted data in TLS."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"The interface of InfluxDB is so complex and should be made easier for non-technical people."
 

Pricing and Cost Advice

"The price of the solution is reasonable."
"Price-wise, I have no information on how much Azure Network Watcher costs."
"The pricing is good. It's not too expensive."
"Azure Network Watcher is a little bit expensive."
"We are using the open-source version of InfluxDB."
"The tool is an open-source product."
"InfluxDB is open-source, but there are additional costs for scaling."
"InfluxDB recently increased its price. It is very expensive now."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Construction Company
10%
Government
6%
Comms Service Provider
6%
Financial Services Firm
12%
Comms Service Provider
10%
Manufacturing Company
10%
University
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Large Enterprise7
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise8
 

Questions from the Community

What is your experience regarding pricing and costs for Azure Network Watcher?
I do not have the exact setup cost information on hand, but it is available in the public Azure portal. You can access the calculator there to get detailed pricing information.
What needs improvement with Azure Network Watcher?
The main area for improvement is AI-based features. Currently, many intelligent tools are coming from third parties, and Azure Network Watcher needs to improve in this area. The focus should be on ...
What is your primary use case for Azure Network Watcher?
Azure Network Watcher is used for monitoring network traffic. It provides insight into egress and ingress traffic, which helps determine whether consumption can be controlled. Most Azure services c...
What needs improvement with InfluxDB?
InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage. InfluxDB is not suitable for relational databases lik...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is storing a time series database and analyzing data changes over time. I use InfluxDB to store my infrastructure and application metrics, logs, events, and data, and ...
What advice do you have for others considering InfluxDB?
I would advise others looking into using InfluxDB that if they want to store a time series database for monitoring, logging, and event-based tasks, and also want long-term retention of the database...
 

Overview

 

Sample Customers

Information Not Available
ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Find out what your peers are saying about Azure Network Watcher vs. InfluxDB and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.