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)
Pro
Contact sales team
Enterprise
Contact sales team
Offerings
Pricing Offerings
Logstash
New Relic
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Logstash
New Relic
Considered Both Products
Logstash
No answer on this topic
New Relic
Verified User
Engineer
Chose New Relic
Elasticsearch with its Beats technology is open source and has good community support. Amazon CloudWatch is another good alternative if you are using AWS because then the metrics are right there. In fact, I like CloudWatch especially because it is mostly free for basic use and …
Perfect for projects where Elasticsearch makes sense: if you decide to employ ES in a project, then you will almost inevitably use LogStash, and you should anyways. Such projects would include: 1. Data Science (reading, recording or measure web-based Analytics, Metrics) 2. Web Scraping (which was one of our earlier projects involving LogStash) 3. Syslog-ng Management: While I did point out that it can be a bit of an electric boo-ga-loo in finding an errant configuration item, it is still worth it to implement Syslog-ng management via LogStash: being able to fine-tune your log messages and then pipe them to other sources, depending on the data being read in, is incredibly powerful, and I would say is exemplar of what modern Computer Science looks like: Less Specialization in mathematics, and more specialization in storing and recording data (i.e. Less Engineering, and more Design).
I have used New Relic in different scenarios like monitoring my production infrastructure and applications which helps us to reduce the downtime of my applications and websites and also I have used the synthetic monitoring feature which helps to proactively monitor our websites availability. Along with this I have also used New Relic for cloud resources cost monitoring which helps to reduce my cloud cost. Also I have used mobile application monitoring which helps me to trace the sessions easily and I can easily reduce my RCA through the help of that.
Logstash design is definitely perfect for the use case of ELK. Logstash has "drivers" using which it can inject from virtually any source. This takes the headache from source to implement those "drivers" to store data to ES.
Logstash is fast, very fast. As per my observance, you don't need more than 1 or 2 servers for even big size projects.
Data in different shape, size, and formats? No worries, Logstash can handle it. It lets you write simple rules to programmatically take decisions real-time on data.
You can change your data on the fly! This is the CORE power of Logstash. The concept is similar to Kafka streams, the difference being the source and destination are application and ES respectively.
New Relic APM allows us to follow up transactions across services and trace performance bottlenecks in real-time, crucial when monitoring the processing of energy loads or predictive maintenance algorithms.
It gives us deep visibility into our cloud servers, containers and IOT gateways, so we can catch CPU spikes or memory leaks which can impact the data we ingest from the field devices.
We develop custom dashboards for monitoring trends of power consumption, abnormality in sensors and API health. In conjunction with alerting, it makes sure we are fixing issues before customers even see them.
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 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
I have given this much rating as I am used New Relic in different sectors and for different use cases like its K8s monitoring, infra monitoring, full stack monitoring as compare to other tools New Relic gives data in a formatted and connected way, and also it is giving us value for money. It also launches new features day by day which helps users to track the issue very quickly. It also supports OTel integrations which is the latest trend of observability tools. thats why I had given this much rating to New Relic.
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
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.
Logstash can be compared to other ETL frameworks or tools, but it is also complementary to several, for example, Kafka. I would not only suggest using Logstash when the rest of the ELK stack is available, but also for a self-hosted event collection pipeline for various searching systems such as Solr or Graylog, or even monitoring solutions built on top of Graphite or OpenTSDB.
New Relic has full stack visibility and gives us all options for observability like one stop shop. It gives you front end, backend as well synthetic monitoring capabilities. Every other feature built into one cost model (usually) which ties to data that you send, it helps you leverage all features without having to pay additional charge for feature
Positive: LogStash is OpenSource. While this should not be directly construed as Free, it's a great start towards Free. OpenSource means that while it's free to download, there are no regular patch schedules, no support from a company, no engineer you can get on the phone / email to solve a problem. You are your own Engineer. You are your own Phone Call. You are your own ticketing system.
Negative: Since Logstash's features are so extensive, you will often find yourself saying "I can just solve this problem better going further down / up the Stack!". This is not a BAD quality, necessarily and it really only depends on what Your Project's Aim is.
Positive: LogStash is a dream to configure and run. A few hours of work, and you are on your way to collecting and shipping logs to their required addresses!
