

InfluxDB and New Relic compete in time-series data handling and performance monitoring. InfluxDB has an edge with its ease of deployment and cost-effectiveness, while New Relic balances higher pricing with comprehensive features.
Features: InfluxDB provides robust time-series data storage, high granularity, and scalability, making it ideal for IoT and analytics. It supports a flexible query language and integrates easily with existing systems. New Relic offers extensive application performance monitoring, delivering deep insights into system health with detailed performance metrics. It includes anomaly detection and supports a wide range of technology integrations.
Room for Improvement: InfluxDB could enhance its analytics capability, improve data visualization tools, and expand community support channels. New Relic could simplify its initial configuration, offer more competitive pricing plans, and improve real-time data processing speeds.
Ease of Deployment and Customer Service: InfluxDB offers a straightforward setup with an intuitive interface, suitable for developers. New Relic requires more complex configuration, but it provides comprehensive customer support to assist with challenges during setup.
Pricing and ROI: InfluxDB appeals to those with budget constraints due to its lower initial costs and effective data handling capabilities, offering significant ROI. New Relic, with a higher pricing tier, justifies costs through its powerful monitoring suite and the potential for high ROI by improving system performance insights.
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.
There is return on investment because since we reduced the downtime, we can definitely save a lot of money within that period.
There is a definite return on investment for New Relic, as we would not have invested in building its infrastructure if there were no returns.
One of the metrics that helped as a return on investment was the ability to detect issues faster and troubleshoot more quickly, which in turn helped to achieve a much better service level agreement with customers.
If I drop an email to them, they will respond quickly to my email.
Customer support from New Relic is very good, and we rarely need to create support tickets.
They are very polite and helped him out.
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.
We currently use New Relic for tens of thousands of developers and hundreds of teams within our organization, and we have not encountered any scalability issues.
It is also suitable for cloud native architectures, SaaS, or software as a service, and for high volume data ingestion also.
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.
New Relic lags sometimes.
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.
If they could improve the customer support by reducing their SLA within three to five days, if they could remediate everything, that will be so much helpful.
Using real-time data, if there are any malicious patterns or something happening, they can identify those.
Because of the pricing model, organizations have experienced uncontrolled costs and were not able to afford New Relic.
We use the open-source version of InfluxDB, so it is free.
My experience with pricing, setup cost, and licensing for InfluxDB was great, as I did not use any license.
Considering the features New Relic offers, the pricing or cost setup has not been a blocker for our budget.
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.
Using New Relic speeds up troubleshooting and resolution, giving us a clearer picture of where issues are, thus saving time and effort.
New Relic is very useful for teams that don't have much of a dedicated DevOps team but want to have observability for their platform, and it's an easy way to get started.
New Relic has positively impacted our organization by reducing errors, improving performance, and saving time.
| Product | Market Share (%) |
|---|---|
| New Relic | 1.5% |
| InfluxDB | 0.3% |
| Other | 98.2% |

| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 3 |
| Large Enterprise | 8 |
| Company Size | Count |
|---|---|
| Small Business | 65 |
| Midsize Enterprise | 50 |
| Large Enterprise | 70 |
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.”
New Relic offers real-time application monitoring and insight into performance bottlenecks. Its customizable dashboards and APM integration provide efficient operational support, while server performance alerts ensure quick issue detection.
New Relic provides comprehensive monitoring of application performance, tracking bottlenecks across databases and front-end components. Users employ it for server and infrastructure monitoring, as well as analyzing key metrics such as CPU and memory usage. The solution's ability to integrate with tools like PagerDuty enhances incident management capabilities. However, users have expressed a need for improvements in query language simplicity, more detailed historical insights, and better mobile app monitoring support.
What are New Relic's most important features?In industries like e-commerce and financial services, New Relic supports application performance monitoring to enhance user experience and system reliability. Organizations leverage its insights for optimizing performance, particularly in server operations and infrastructure management. Its ability to monitor API failures through synthetic monitoring is crucial for maintaining high service levels.
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.