The InfluxDB is a time series database from InfluxData headquartered in San Francisco. As an observability solution, it is designed to provide real-time visibility into stacks, sensors and systems. It is available open source, via the Cloud as a DBaaS option, or through an Enterprise subscription.
N/A
New Relic
Score 8.6 out of 10
N/A
New Relic is a SaaS-based web and mobile application performance management provider for the cloud and the datacenter. They provide code-level diagnostics for dedicated infrastructures, the cloud, or hybrid environments and real time monitoring.
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
Pricing
InfluxDB
New Relic
Editions & Modules
No answers on this topic
Free (Forever)
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
Telemetry Data Platform
$0.25
per month per extra GB data ingest (after first free 100GB per month)
Incident Intelligence
$0.50
per month per event (after first 1000 free events per month)
Standard
$99
per month per full user (after first free full user - unlimited free basic users)
InfluxDB is much easier to initially setup and scale compared to Graphite (now known as Whisper). With a smaller team we found Graphite too much overhead that would make operational support a significant blocker or generation of technical debt.
InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).
Any web dev would find New Relic useful. The application performance monitoring and transaction tracing tools let you identify the root causes of a slow web site or application and give you the opportunity to fix any bottlenecks. I can't think of a scenario where New Relic is not appropriate - I use it on every web site I develop and manage.
gives us an monitoring of all our underlying servers and also we can configure some alerts upon them like CPU and memory alerts.
Kubernetes cluster monitoring with new relic for EKS gives us and minute details of our cluster utilisation like node usage, pods memory request and limits
Network traceability for each and every request with response time analysis is great we can trace which component is responsible for generating response delay
log managements of the logs the infrastructure is generating we can view logs through there only
I would like to see sort of simulator inside the user interface, that way we can send requests directly from it to test some configuration instead of setting up a test environment in our end.
It would be nice if the data ingestion can be filtered by APM's. That way we can know which application is ingested most data.
It would be nice if we could ingest logs (apache, system logs, and other logs) and correlate them with the APM.
InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.
The only issue that we have had with New Relic is that the price might be a little expensive for smaller companies. The amount of data you store in New Relic impacts the cost, and can get away from you if you don't work closely with the vendor. Overall though the application is top notch.
As an engineer, New Relic has been very quick and easy for me to pick up/install/use. It has been less easy for some of the less technical-minded folks in our organization and their UI still is inconsistent multiple years after refactoring their platform to be New Relic One.
We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.
There are times I feel that the initial support is lacking. And in some cases the automated responses of not hearing anything are annoying if the reason why there has been no movement is because we are still waiting to hear back from NR support. So, i think they should loose the automation as it can seem disingenuous
It's better to start by implementing New Relic in one project and test everything. Try to follow best recommended practices and read all the official documentation. Everything seems well tested. Then, start by installing agents to the rest of your projects and keep a close look to all logs and metrics New Relic gives you.
To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).