Summary of pricing information.

Tanzu Observability by Wavefront pricing depends on the contract that your company has with VMware, on the types on data you’re ingesting, and on some other factors. This page gives an overview of pricing for the different types of data you can send to Wavefront.

Pricing Structure

At the core of the model is the idea of consumption-based pricing. What you pay is based on data throughput, primarily:

  • Data ingestion. When the Wavefront service ingests data, the data is consumed and count toward your allocation.
  • Data scanning. When you run a query, either as part of an alert or when you look at a dashboard, the backend has to scan the data. Scanning counts toward your allocation.

The model has this basic pricing structure:

  • Each ingested or scanned metric or derived metric counts as 1 PPS.
  • Each ingested or scanned histogram or derived histogram counts as 7 PPS.

For scans, the pricing structure is as follows:

  • If intelligent sampling is turned on, the trace data is counted as derived metrics (1 PPS) or derived histograms (7 PPS).
  • If you turn off intelligent sampling, or if you specify trace sampling policies to specifically include certain traces, each tracing span counts as 22 PPS.
  • Span logs are free.

Metrics 1pps and Histograms 7pps are the basis, distributed tracing is 22 PPS if intelligent sampling is turned off

Data Retention

Default data retention is:

  • 18 months for metrics and derived metrics.
  • 6 months for histograms and derived histograms.
  • 7 days for traces, spans, and span logs.

Some companies negotiate a longer data retention at a higher price. Ask your administrator for details.

Learn More