What is the typical pricing model for observability software?

Typical pricing models for observability software Observability software is typically priced using a hybrid, consumption-based model: customers pay based on the infrastructure they monitor, the telemetry data they collect, and sometimes the number of people using the platform. The five most common pricing models are: Common pricing models Pricing model How it works Typical billing unit ------------------------ Per host / infrastructure Pay for each monitored server or instance $/host/month Data…

1. Datadog — For example, Datadog separates APM host pricing from indexed log events and log storage.
2. New Relic — New Relic combines ingestion and user licensing.
3. Splunk — Splunk – Observability Pricing.
4. Grafana — Grafana Cloud – Pricing Documentation.

The typical pricing model for observability software is hybrid: a recurring subscription or platform fee combined with usage-based charges for the telemetry processed. Common pricing dimensions include: Data ingestion: Logs, metrics, traces, spans, or events, usually priced per GB, TB, or million events. Infrastructure: Number of hosts, servers, containers, nodes, or agents monitored. Users or seats: Number and type of engineers, developers, or other platform users. Services or workloads:…

Observability software vendors typically do not rely on a single, one-size-fits-all approach .

1. New Relic — Instead, according to industry resources like New Relic's Pricing Whitepaper , most platforms use a hybrid pricing model combining quantity-based metrics with consumption-based telemetry .
2. Datadog — (Examples: Datadog, Dynatrace) Telemetry / Data Ingestion-Based Pricing A usage-based model where you pay for the volume of data collected, typically measured in gigabytes (GB) or terabytes (TB) ingested across metrics,…
3. Dynatrace — (Examples: Datadog, Dynatrace) Telemetry / Data Ingestion-Based Pricing A usage-based model where you pay for the volume of data collected, typically measured in gigabytes (GB) or terabytes (TB) ingested across metrics,…
4. Splunk — (Examples: New Relic flat-rate ingest tiers, Splunk/Elastic log-heavy models) User-Based / Seat Pricing Charges based on the number of provisioned seats (e.g., core engineers, developers, or read-only stakeholders…
5. Elastic Observability — (Examples: New Relic flat-rate ingest tiers, Splunk/Elastic log-heavy models) User-Based / Seat Pricing Charges based on the number of provisioned seats (e.g., core engineers, developers, or read-only stakeholders…