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.7
Number of Reviews
19
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), IT Infrastructure Monitoring (15th), NoSQL Databases (6th)
 

Mindshare comparison

As of April 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.4%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
InfluxDB0.4%
Azure Network Watcher0.5%
Other99.1%
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

"The most valuable features I have found are typology, visualization, and capture."
"It provides good visibility."
"The solution is stable, there are no bugs or glitches and it doesn't crash or freeze, it's reliable."
"The solution is stable."
"This is a stable system providing stable performance."
"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 provides valuable features based on your specific requirements and use cases, helping you monitor network bandwidth, throughput, data flow consumption, and control costs by giving insight into egress and ingress traffic, total input and output operations, bandwidth, and threats through IP identification."
"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."
"My advice for others looking into using InfluxDB is to use it the same way I did, because it is really stable, easy and friendly to use, and it is a great product overall."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"This product has been working well and it is serving our purpose, so I can recommend it to others."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"The solution is very powerful."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
 

Cons

"Lacks sufficient security features."
"The initial setup and deployment could be improved to be simplified."
"Azure Network Watcher could improve by having other built-in applications, for example, an application to log activities for inbound and outbound traffic."
"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 initial setup and initial learning curve could be improved to be easier."
"Azure is good, however, the Fortinet GUI is more intuitive and I like it more than anything else."
"Azure is good, however, the Fortinet GUI is more intuitive and I like it more than anything else."
"Azure Network Watcher could improve by having other built-in applications. For example, an application to log activities for in and outbound traffic."
"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."
"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."
"Sometimes, when we write too much data within a minute, the data count becomes excessive, reaching perhaps 100,000 or 500,000 data points, and InfluxDB gives a timeout exception, which we must handle in our application."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"The error logging capability can be improved because the logs are not very informative."
"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

"Azure Network Watcher is a little bit expensive."
"Price-wise, I have no information on how much Azure Network Watcher costs."
"The pricing is good. It's not too expensive."
"The price of the solution is reasonable."
"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."
"We are using the open-source version of InfluxDB."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
886,349 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Construction Company
10%
Government
6%
University
6%
Financial Services Firm
13%
Manufacturing Company
10%
Comms Service Provider
9%
University
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Large Enterprise7
By reviewers
Company SizeCount
Small Business8
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?
One thing I appreciate about InfluxDB is its balance between performance and ease of use, especially with Flux making complex queries accessible. However, I do wish the documentation and community ...
What is your primary use case for InfluxDB?
My main use case for InfluxDB has been mostly for monitoring and analyzing the time-series data related to system metrics, and also tracking logs and API performance. In my current role, I use it t...
What advice do you have for others considering InfluxDB?
My advice for others looking into using InfluxDB would be to clearly define their time-series data use cases upfront to ensure that InfluxDB fits their needs, especially for high-frequency metrics ...
 

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.
886,349 professionals have used our research since 2012.