

InfluxDB and DX NetOps compete in data management and network operations. While InfluxDB is favored for its pricing and support, DX NetOps's comprehensive features offer significant value.
Features: InfluxDB handles high-performance time-series data, making it ideal for database management and IoT. It focuses on efficient data ingestion and query handling, and has flexibility with open-source integration. DX NetOps provides network performance monitoring, extensive visibility across network components, and sophisticated analytics with troubleshooting tools. The primary distinction is InfluxDB’s data-centric approach versus DX NetOps’s network analysis emphasis.
Room for Improvement: InfluxDB could enhance user-friendly interfaces, expand direct support options, and improve real-time data visualization tools. DX NetOps may benefit from reduced pricing tiers, streamlined setup processes, and more flexible integration with third-party tools.
Ease of Deployment and Customer Service: DX NetOps offers a scalable deployment model for large enterprises with integrated customer support for seamless implementation. InfluxDB provides flexibility via its open-source model for easy integration into various environments. However, DX NetOps features direct support channels for enhanced troubleshooting efficiency, while InfluxDB relies on community-driven assistance.
Pricing and ROI: InfluxDB provides a cost-effective solution with rapid setup and scalable pricing, delivering high ROI in data-intensive applications. DX NetOps requires a higher upfront investment but enhances network operational efficiency and delivers favorable ROI for network-focused enterprises. InfluxDB targets data-focused operations, while DX NetOps caters to network management.
It can save you the cost of the product by reducing expenses and downtimes in 12 to 18 months.
It simplifies processes and reduces the need for additional employees.
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.
Time saved is there, as I mentioned, because we have an analytics system from where we get alerting and monitoring.
They are fast, responsive, and have technical expertise.
Everything about DX NetOps is perfect, including the interface, technical support, and pricing.
Creating a support case based on priority allows for immediate responses.
Obtaining that quantity of data directly from InfluxDB is quite challenging, and that is why we ask for help from the InfluxDB team to retrieve the data to avoid timeouts and those kinds of issues.
The product is very scalable, to the maximum.
The main challenge with InfluxDB, which is common with all databases, was handling very high throughput systems and high throughput message flow.
We’ve scaled on volume with seven years of continuous data without performance degradation.
InfluxDB's scalability is fine for me; I gather a lot of metrics and have not had any issues.
I rate the stability of the product as ten on a scale of one to ten, indicating that it is very stable.
It serves as the backbone of our application, and its stability is crucial.
It is very stable, with no reliability or downtime in InfluxDB.
After integrating Kafka, it never broke again, as Kafka handled messages and metrics appropriately, decreasing the message throughput.
DX NetOps is somewhat convoluted, and some of the programming constructs can be documented or driven through languages such as Python, Perl, and shell scripting, but they have their proprietary language, which may not be very user-friendly.
Different communication methods such as agent-based connections, TCP/IP, or secured connections are necessary—features not currently available in DX NetOps and Spectrum.
I would particularly like it to integrate with the Symantec portfolio and the Carbon Black portfolio.
InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying.
Having a SQL abstraction in InfluxDB could be beneficial, making it more accessible for teams that prefer querying with SQL-style syntax.
It could include automated backup and a monitoring solution for InfluxDB or a script developed by a REST API.
The licensing cost of DX NetOps is expensive, not very affordable, and on the top of the price range in the market.
I think the pricing is expensive.
We use the open-source version of InfluxDB, so it is free.
I find the cloud version pricing of InfluxDB reasonable, and for the on-premises solution we use in our service, we need to purchase licenses.
My experience with pricing, setup cost, and licensing for InfluxDB was great, as I did not use any license.
The product features include automation through AI, allowing out-of-the-box analysis of performance data, building baseline trends, and enabling configuration of dynamic thresholds relative to collected data.
The best features I've seen so far with DX NetOps are that it can work with large scale systems, and it has a lot of functionalities and matrices.
The most valuable feature in DX NetOps is the topological view, which is the network topological view.
The most important feature for us is low latency, which is crucial in building a high-performance engine for day trading.
InfluxDB’s core functionality is crucial as it allows us to store our data and execute queries with excellent response times.
It helps me maintain my solution easily because it is very reliable, so we didn't face any performance issues or crashes regarding our queries; we can get the results very fast.
| Product | Market Share (%) |
|---|---|
| InfluxDB | 0.3% |
| DX NetOps | 0.7% |
| Other | 99.0% |


| Company Size | Count |
|---|---|
| Small Business | 4 |
| Midsize Enterprise | 1 |
| Large Enterprise | 5 |
| Company Size | Count |
|---|---|
| Small Business | 6 |
| Midsize Enterprise | 3 |
| Large Enterprise | 8 |
DX NetOps by CA Technologies, a Broadcom company, improves your time to value through advanced AI capabilities and unified network visibility that delivers simplified NetOps intelligence into the user experience that traverses modern architectures. DX NetOps accomplishes this through high scale, unified network monitoring that enables full-stack analytics for assuring traditional and modern architectures. DX NetOps converts inventory, topology, device metrics, faults, flow and packet analysis into actionable intelligence for network operations teams. Complimented by our AIOps solution, DX NetOps enables IT teams to establish proactive, autonomous remediation capabilities across the applications, infrastructure, and networks that fuel superior user experiences.
InfluxDB is open-source software that helps developers and enterprises alike to collect, store, process, and visualize time series data and to build next-generation applications. InfluxDB provides monitoring and insight on IoT, application, system, container, and infrastructure quickly and easily without complexities or compromises in scale, speed, or productivity.
InfluxDB has become a popular insight system for unified metrics and events enabling the most demanding SLAs. InfluxDB is used in just about every type of industry across a wide range of use cases, including network monitoring, IoT monitoring, industrial IoT, and infrastructure and application monitoring.
InfluxDB offers its users:
InfluxDB Benefits
There are several benefits to using InfluxDB . Some of the biggest advantages the solution offers include:
Reviews from Real Users
InfluxDB stands out among its competitors for a number of reasons. Two major ones are its flexible integration options and its data aggregation feature.
Shalauddin Ahamad S., a software engineer at a tech services company, notes, “The most valuable features are aggregating the data and the integration with Grafana for monitoring.”
We monitor all Network Monitoring Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.