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
Logstash
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)
Logstash is a must in an ELK stack, which I am sure is going to be the #1 case. At any point when you have several sources, Logstash can be the common point to aggregate, and categorize those data. Then send this new data to its destination. Very handy. It is free and open source. It may not be appropriate to analyze data-sets dependent on each other but from a different data source. Reason being Logstash works on data at hand, and not wait for other data to arrive. It would be unwise for Logstashh to handle complicated, long-running transformations because this is injected and ejected. The faster you do it, the safer.
It is perfect for observing our energy platforms during high-load situations, such as grid demand spikes, or our real-time ingest of sensor data, allowing us to respond in real time to anomalies. And it’s a good way to monitor API performance in client dashboards, too. But it’s not as conducive for low-budget/low-code work or deep customization that doesn’t get ample development support given its complexity and expense.
Capturing Front end Metrics specially web vitals and setting up alerts for violations really helps.
NRQL is great tool to fetch the data you need. With queries you can pull the data and put the data by table or by chart. You can even trend graphs and create dashboards.
Synthetic Monitoring is very helpful for proactive monitoring. You can use it for user journeys by using scripted browser monitor type or just check availability using PING type.
ASk AI is great addition that can fetch details you need with natuaral language
Memory: Logstash is a HOG, if you are deploying it on commodity (i.e. cheap and old) hardware: You will need at least 2GB, just for Logstash. So don't expect to run your entire ELK stack on one AMD Athlon machine.
Overlap: Logstash fills in an area of the ELK stack that makes the most sense: as a log file transformer / shipper. However, if you start breaking that stack, with the addition of other components- you start seeing where features of Logstash may be implemented or solved in the additional components much easier (or better, or to a higher degree of resolution)
More Overlap: Since my team employs Syslog-ng extensively- Logstash can sometimes get in the way (and this may be a problem for DevOps stacks overall): You can configure Syslog to record certain information from a source, filter that data, and even export that data in a particular format. Logstash will pick that data up, and then parse it. However, if you don't keep your Syslog-ng configuration files, and your Logstash configuration files in sync, your results will not be what you expected, and this will translate into (sometimes) hours/days of work, hunting down a line item in a configuration file.
I have not yet found any similar product that offers me this range of features to help us keep our online service fast and reliable. Besides this, New Relic is constantly evolving by adding new plugins to emerging technologies and platforms. Server performance measuring features are a key point as our user database grows.
As I said earlier, for a production-grade OpenStack Telco cloud, Logstash brings high value in flexibility, compliance, and troubleshooting efficiency. However, this brings a higher infra & ops cost on resources, but that is not a problem in big datacenters because there is no resource crunch in terms of servers or CPU/RAM
New Relic helps in observability setup for the critical environments and getting known about the issues and troubleshoot the applications and services. Alerts helps in knowing the abnormal state of the system and services, Dashboards are used for visualizing the key metrics and muting the unwanted notifications and dropping the extra data from the source.
The support team has been really helpful and resolved most of the issues on time. However, for a couple of issues, several follow-ups were needed to elicit a reasonable response. The issue was deeply technical and could have been investigated only by their Architects, and bringing them into the ticket took longer than needed
The documentation was clear and concise; the only issue we ran into was custom application naming. Due to HTTPD mod_fcgid and the need for the application name to be set in php.ini (not in .htaccess or the virtual host directive) ... we had issues setting this up.
MongoDB and Azure SQL Database are just that: Databases, and they allow you to pipe data into a database, which means that alot of the log filtering becomes a simple exercise of querying information from a DBMS. However, LogStash was chosen for it's ease of integration into our choice of using ELK Elasticsearch is an obvious inclusion: Using Logstash with it's native DevOps stack its really rational
Its covers all the observability aspects as well as giving us more competitive pricing models compared to other providers that's why I like to use New Relic in place of other tools. And also it introduces new Agentic AI features as well as it adopts AI in its RCA. As an observability tool it should reduce the RCA of any problem and New Relic is continuously focusing on that that's why I am preferring New Relic in place of other tools.
It is very difficult to give any figures on ROI, as it depends on many factors, and in a Telcocloud environment, it is much complex to find out; however, I would give some points below on ROI
ROI based on flexibility is very high, as it reduces the time to find RCA
ROI based on integration is very high because it supports multi-vendor environments, avoiding vendor lock-in & works across multi-cloud setups
ROI on resource consumption is less because Logstash in 2-3 times more resource-intensive as compared to its lightweight alternatives resulting in latency
