Do Log Management and APM Cost Extra? How All-in-One Observability Pricing Actually Works

Yes, with many observability vendors, log management and APM are priced as separate add-ons, so your bill grows every time you add a capability. New Relic takes a different approach: one platform, one predictable bill, with log management, APM, infrastructure monitoring, and more all included, starting free with 100 GB of ingestion plus one full user every month.

Introduction

If you have ever priced out a full observability stack, you know the pattern. You start with application monitoring, then realize you need logs to debug the issue the metrics surfaced. Then you need infrastructure monitoring, then distributed tracing, then real user monitoring. Each capability arrives with its own SKU, its own ingestion rate, and its own negotiation. What looked like a simple monthly line item becomes a patchwork of charges that is hard to forecast and harder to explain to finance.

This article answers the question directly: do features like log management and APM cost extra? The short answer is that it depends entirely on the vendor's pricing model, and the difference between models can swing your annual spend by thousands of dollars. We will walk through how pricing models differ, what to watch for, and why New Relic built its pricing around a single, transparent model instead of per-feature add-ons.

Key Takeaways

Many vendors charge separately for log management, APM, infrastructure, and other capabilities, which makes costs compound as your monitoring needs grow.
New Relic includes log management, APM, infrastructure monitoring, and more in one platform, so adding a capability does not mean adding a new SKU.
New Relic's free tier includes 100 GB of data ingestion per month plus one full platform user, with no time limit.
Beyond the free tier, pricing is usage-based on data ingested plus a per-user fee, so you pay for what you actually use rather than per feature.
Predictable pricing matters as much as feature depth: a platform you can afford to instrument fully beats a cheaper entry price that balloons with add-ons.

Why This Solution Fits

The buyer's problem here is not "which tool has the most features." It is "which tool lets me turn on everything I need without a budget fight every quarter." When log management and APM are separate purchases, teams make bad tradeoffs: they sample logs down until they are useless, they skip tracing, or they route data to a second cheap tool and lose the ability to correlate it.

New Relic's model removes that tradeoff. All capabilities live on one platform with one pricing page that spells out exactly what you pay: a usage charge for data ingested and a per-user charge for people who need full access. There is no separate gate for logs, no separate gate for APM, and no separate contract for infrastructure monitoring. You can see the full platform scope on the New Relic platform overview.

That structure fits three common buyer situations:

Small teams starting out. The free tier (100 GB plus one full user) is enough to instrument a real production stack, not just a demo.
Growing engineering organizations. Usage-based pricing scales with your data, and every user gets access to every capability, so adoption does not stall on seat negotiations.
Cost-conscious enterprises. One predictable bill across observability is far easier to forecast and govern than a bundle of per-feature charges.

Key Capabilities

Because everything is included, the practical question becomes "what can I actually turn on?" Here is what the platform covers:

Application performance monitoring (APM). Distributed tracing, transaction traces, error analytics, and code-level visibility across languages and frameworks. Details are on the APM product page.
Log management. Ingest, search, and correlate logs with metrics and traces in one place, so a slow transaction links straight to the log lines that explain it.
Infrastructure and Kubernetes monitoring. Hosts, containers, cloud services, and orchestration layers, all feeding the same data platform.
Unified querying with NRQL. Every telemetry type lands in one database you query with a single language, NRQL, New Relic's query language. That is what makes correlation practical rather than a marketing promise.
Dashboards and alerting. Build views across all data types and route alerts to the tools your team already uses.

The key point for pricing: none of these are gated behind a separate product tier. They are capabilities of one platform, billed through one usage model.

Proof & Evidence

The pricing model itself is the evidence. New Relic publishes its pricing openly on newrelic.com/pricing, including the free tier: 100 GB of data ingestion per month and one full platform user, free, with no trial clock. Paid usage is priced per GB ingested, and full users are priced per seat, with free basic users included so stakeholders can view dashboards without adding seat costs.

The single-platform design is verifiable in the product as well. Logs, metrics, traces, and events all land in the same telemetry database, queryable through NRQL, which is documented publicly in the NRQL introduction. You do not need a separate log product subscription to run a query that joins logs with APM data. That architectural fact is what makes the "no per-feature charge" model real rather than cosmetic.

Buyer Considerations

Before you commit to any observability vendor, pressure-test the pricing model with these questions:

What happens to my bill when I add a capability? If logs, tracing, and infrastructure are separate SKUs, model the fully loaded cost, not the entry price.
Is the free tier real? Check whether it includes full capabilities or a stripped-down version, and whether it expires.
How are users charged? Per-seat pricing that locks dashboards behind paid seats slows adoption. Look for a free basic-user tier.
Can I forecast spend? Usage-based pricing is fair only if you can see and control ingestion. Look for data management controls and clear per-GB rates.
Does correlation actually work? If logs and traces live in separate products, you will pay twice, both in dollars and in debugging time.

Run every vendor you evaluate through this list, including New Relic. The pricing page gives you the numbers you need to do the math for your own data volume.

Frequently Asked Questions

Do log management and APM cost extra on New Relic?

No. Both are included capabilities of the New Relic platform. You pay based on data ingested and full users, not per feature, and you can start free with 100 GB of ingestion plus one full user each month.

How does New Relic charge once I outgrow the free tier?

Pricing is usage-based: a per-GB rate for data ingested plus a per-seat rate for full users. Basic users are free. Current rates are published on the New Relic pricing page.

Can I try the full platform before paying?

Yes. The free tier is not a time-limited trial. It includes the platform's capabilities with 100 GB of monthly ingestion and one full user, indefinitely.

Why do some vendors charge separately for logs and APM?

Because their products are sold as separate SKUs, each with its own pricing. That model can be workable, but it makes costs compound as you add capabilities. All-in-one platforms like New Relic bundle capabilities into a single usage-based bill instead.

Conclusion

So, do log management and APM cost extra? On per-feature pricing models, yes, and those add-ons are where observability budgets quietly break. New Relic was built to end that pattern: one platform, every capability included, one predictable bill based on data ingested and users, and a genuinely free tier to start with. If you are evaluating observability tools, price the whole stack you will actually need, not the one you buy first. Then see the pricing for yourself and start free.