Logging · head to head
Fluentd vs New Relic Logs
The short version
- Each has a real cost: Fluentd fluentd needs more than 60 MB of memory at runtime, against roughly 450 KB for Fluent Bit; New Relic Logs log data counts against the same 100 GB monthly free ingest allowance shared with every other telemetry type, so logs compete with metrics and traces for it
- They diverge on capability: Fluentd covers Log collection, New Relic Logs covers Log ingestion.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which Fluentd and New Relic Logs actually diverge.
| Attribute | Fluentd | New Relic Logs |
|---|---|---|
| Pricing model | open-source | freemium |
| Founded | 2011 | 2008 |
Identical on both: starting price (Free), free tier (Yes), platforms (Web, Api), user rating (Not yet rated), category (Logging).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Fluentd
- Log collection
- Data parsing
- Filtering and buffering
- Event routing
Only in New Relic Logs
- Log ingestion
- Full-text search
- Logs-in-context
- Custom dashboards
Both cover
- API
- Webhooks
- REST
- Web support
- Api support
What people use each for
The jobs each tool is most often brought in to do.
Fluentd
- Unified log collection and routing from many sources to many destinationsnot New Relic Logs
- Parsing and transforming log records before forwardingnot New Relic Logs
- Aggregating logs from containers into Elasticsearch, S3 or a SIEMnot New Relic Logs
New Relic Logs
- Centralised log management alongside metrics and tracesnot Fluentd
- Searching and alerting on application logs in context with performance datanot Fluentd
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Fluentd
- Fluentd needs more than 60 MB of memory at runtime, against roughly 450 KB for Fluent Bit
- Fluentd is built as a Ruby gem and depends on other gems, so a Ruby runtime is required
- Its capability comes from over 1,000 external plugins rather than built in functionality, so each added input or output is a separate dependency
- The Fluent Bit documentation states that cloud providers have switched from Fluentd to Fluent Bit for performance and compatibility and calls Fluent Bit the next generation solution
New Relic Logs
- Log data counts against the same 100 GB monthly free ingest allowance shared with every other telemetry type, so logs compete with metrics and traces for it
- Ingest beyond that is $0.40 per GB, rising to $0.60 per GB on the Data Plus option
- Full platform users cost $349 each a month on Pro with an annual commitment, or $418.80 paying monthly
- The Standard edition caps additional full platform users at 5
- Core users are $49 a month each even though basic users are free
Pricing, plan by plan
Fluentd
Free- FreeFree
- Log collection
- Data parsing
- Filtering and buffering
New Relic Logs
Free- Free TierFree
- 100 GB per month data ingest
- Unlimited basic users
- 1 full platform user
- Standard Edition$49/month
- Up to 5 full platform users
- Core users 49 dollars per user per month
- Additional full platform users at 99 dollars each
- Pro Edition$349/year
- Unlimited full platform users
- Core users at 49 dollars per user per month
- Full platform users at 349 dollars per user annually or 418.80 dollars monthly
- Enterprise Edition$null/mo
- Unlimited full platform users
- Custom pricing
- FedRAMP and HIPAA support
Which should you pick?
Choose Fluentd if
- You need log collection.
- You want to start without paying.
- You work on Web, Api.
- You also want data parsing.
Choose New Relic Logs if
- You need log ingestion.
- You want to start without paying.
- You work on Web, Api.
- You also want full-text search.
Questions people ask
- Is Fluentd or New Relic Logs better?
- Neither clearly leads. Fluentd starts at Free and New Relic Logs at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Fluentd or New Relic Logs?
- Fluentd starts at Free and New Relic Logs at Free.
- Does Fluentd or New Relic Logs run on more platforms?
- Both run on Web, Api, so platform support will not decide this one for you.
- Can I use Fluentd for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Fluentd best used for?
- Fluentd is most often used for unified log collection and routing from many sources to many destinations, parsing and transforming log records before forwarding, aggregating logs from containers into elasticsearch, s3 or a siem. Of those, unified log collection and routing from many sources to many destinations and parsing and transforming log records before forwarding are not what New Relic Logs is typically brought in for.
- What can Fluentd do that New Relic Logs cannot?
- Fluentd covers Log collection, Data parsing, Filtering and buffering, Event routing. New Relic Logs covers Log ingestion, Full-text search, Logs-in-context, Custom dashboards. Both handle API, Webhooks, REST, Web support.
Answered from the vendors’ own pages
Fluentd: How much does Fluentd cost?
Fluentd is free and open-source under the Apache 2 License from the Cloud Native Computing Foundation (CNCF). There are no subscription fees, licensing costs, or commercial pricing tiers.
SourceNew Relic Logs: Is New Relic free?
New Relic offers a free tier with 100 GB per month of data ingest, 1 full platform user, and unlimited basic users.
SourceNew Relic Logs: What does New Relic charge for data beyond the free tier?
New Relic charges 0.40 dollars per gigabyte for data beyond the 100 GB free monthly allowance. Data Plus tier costs 0.60 dollars per GB and includes up to 90-day extended retention.
SourceNew Relic Logs: What is the Pro plan pricing?
The Pro Edition costs 349 dollars per user per year for full platform users, or 418.80 dollars per month. Unlimited full platform users are included.
SourceRelated pages
More on New Relic Logs
Other head to heads
- Fluentd vs New Relic
- Fluentd vs Datadog Logs
- Fluentd vs Elastic Stack
- Fluentd vs Coralogix
- Fluentd vs InfluxDB
- Fluentd vs Graylog
- Fluentd vs Traceloop
- Fluentd vs Splunk Enterprise
- Fluentd vs Honeybadger
- Fluentd vs Humio
- Fluentd vs ELK Stack
- Fluentd vs Telegraf
- Fluentd vs Kibana
- Fluentd vs Logstash
- Fluentd vs Elasticsearch Service
- Fluentd vs Filebeat
- Fluentd vs Dynatrace Logs
- Fluentd vs Loki
- Fluentd vs Mezmo
- Fluentd vs Sematext
- Fluentd vs incident.io
- Fluentd vs Rootly
- Fluentd vs Checkly
- Fluentd vs Sumo Logic
- Fluentd vs Timber
- Fluentd vs Uptime.com
- Fluentd vs Vector
- Fluentd vs Grafana Loki
- New Relic Logs vs New Relic
- New Relic Logs vs Datadog Logs
- New Relic Logs vs Elastic Stack
- New Relic Logs vs Coralogix
- New Relic Logs vs InfluxDB
- New Relic Logs vs Graylog
- New Relic Logs vs Traceloop
- New Relic Logs vs Splunk Enterprise
- New Relic Logs vs Honeybadger
- New Relic Logs vs Humio
- New Relic Logs vs ELK Stack
- New Relic Logs vs Telegraf
- New Relic Logs vs Kibana
- New Relic Logs vs Logstash
- New Relic Logs vs Elasticsearch Service
- New Relic Logs vs Filebeat
- New Relic Logs vs Dynatrace Logs
- New Relic Logs vs Loki
- New Relic Logs vs Mezmo
- New Relic Logs vs Sematext
- New Relic Logs vs incident.io
- New Relic Logs vs Rootly
- New Relic Logs vs Checkly
- New Relic Logs vs Sumo Logic
- New Relic Logs vs Timber
- New Relic Logs vs Uptime.com
- New Relic Logs vs Vector
- New Relic Logs vs Grafana Loki


