APMPriceBook

Per-host vs usage-based observability pricing

By Editorial team · 2026-06-04

In short: Per-host pricing (Datadog, Splunk, Dynatrace) charges a flat fee per monitored host and is predictable for a stable fleet of large hosts but expensive for dense Kubernetes and ephemeral hosts. Usage-based pricing (New Relic, Grafana, Elastic, Coralogix per GB; Sentry, Honeycomb per event) scales with telemetry volume - cheaper for high host density, but it punishes verbose instrumentation. Match the model to how you scale.

Observability vendors split into roughly two pricing philosophies, and picking the wrong one for your architecture is the most common reason bills surprise people. Here is how they differ in 2026.

How the two models work

ModelYou pay forVendorsBest for
Per hostEach monitored host/nodeDatadog, Splunk, DynatraceStable fleet of large hosts
Per vCPUEach monitored coreAppDynamicsCompute-sized billing
Per GB / usageTelemetry data volumeGrafana, Elastic, Coralogix, New RelicDense Kubernetes, ephemeral hosts
Per eventEvents/spans/errorsSentry, HoneycombTrace/error-first, low volume

The Kubernetes problem with per-host

Per-host pricing assumes hosts are few and long-lived. Modern Kubernetes breaks that assumption: you might run dozens of small pods across many nodes, or autoscale hosts up and down by the minute. With per-host billing you pay for every node regardless of how little it emits, and ephemeral hosts can each count. This is why dense-Kubernetes teams often move to usage or per-vCPU models. Compare Datadog vs Grafana Cloud to see the divide in numbers.

The verbose-telemetry problem with usage-based

Usage-based pricing has the opposite failure mode. If your apps log everything at debug level, emit high-cardinality metrics, or trace every request without sampling, your per-GB or per-event bill balloons even on a handful of hosts. Usage models reward disciplined instrumentation and punish noise. See how to cut observability costs for the levers.

A simple decision rule

Bottom line

There is no universally cheaper model - only the right model for your scaling shape. Estimate both in the observability cost calculator and browse the full vendor list. Prices are a June-2026 snapshot; verify on each vendor’s pricing page.

Frequently asked questions

Is per-host or usage-based observability pricing cheaper?

It depends on your workload shape. Per-host is cheaper for a stable fleet of a few large hosts; usage-based is cheaper for many small or ephemeral hosts (dense Kubernetes) because you pay for data, not host count. High telemetry volume can flip it back toward per-host.

Which observability vendors are per-host vs usage-based?

Per-host: Datadog, Splunk Observability, Dynatrace (per host-hour). Per-vCPU: AppDynamics. Per-user + per-GB: New Relic. Usage/per-GB: Grafana Cloud, Elastic, Coralogix, Better Stack, Logz.io, Sumo Logic. Per-event: Sentry, Honeycomb, Last9. Per-monitor: Site24x7.

Related articles

Last updated: 2026-06-04