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
44th
Average Rating
8.0
Reviews Sentiment
5.9
Number of Reviews
14
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
21
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), IT Infrastructure Monitoring (14th), NoSQL Databases (7th)
 

Mindshare comparison

As of June 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

"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."
"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 good for monitoring device behavior."
"The most valuable features I have found are typology, visualization, and capture."
"The stability is very good. I rate it a ten out of ten."
"The solution is stable."
"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."
"Overall, InfluxDB delivered excellent performance, stability, and simplicity for telemetry-driven use cases."
"Based on InfluxDB, we have great analytics produced by our SRE team, and with that, we have an alerting and monitoring system in place."
"Prior to InfluxDB usage, real-time data was not visualized and monitored, and after the introduction of InfluxDB in the entire framework, the organization is benefiting a lot in terms of monitoring and understanding performance data in real-time."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"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."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"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."
 

Cons

"User experience could be improved."
"Technical support from Microsoft needs significant improvement compared to other product vendors."
"Azure Network Watcher needs to have better documentation and it needs to capture information accurately."
"Azure is good, however, the Fortinet GUI is more intuitive and I like it more than anything else."
"I would like to see in the future if we can troubleshoot as a firewall because it is equipment as a network player and some diagnostics."
"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."
"Sometimes, you encounter a VPN tunnel, network, or routing issue, but finding out more about the blockage is challenging."
"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."
"If it gets a little bit more into the metric side, then it would really be great, similar to Prometheus."
"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."
"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."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"However, I cannot ignore the challenges I faced while configuring the database with my message brokers, whether Rabbit or Kafka, because the documentation is not properly provided."
"The error logging capability can be improved because the logs are not very informative."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
Financial Services Firm
24%
Construction Company
11%
Media Company
6%
University
6%
Financial Services Firm
12%
Manufacturing Company
10%
Comms Service Provider
10%
Construction Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise1
Large Enterprise7
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise5
Large Enterprise9
 

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?
If the dashboarding facility can be improved in terms of the visualization parameters and the amount of support available from the community, as well as having smarter alerts to send those alerts t...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is to inject all my performance data and visualize it as a data source into Grafana. My data comes from JMeter from a plugin, which is inserting data to InfluxDB, and ...
What advice do you have for others considering InfluxDB?
It is good to start with InfluxDB to stabilize your data, visualize your data, and have the data stored on a time-series basis. I would recommend everyone to get into InfluxDB and start using it. T...
 

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: June 2026.
899,258 professionals have used our research since 2012.