Learn about deprecated and EOL features and how to prevent potential problems.

Product versions and features move to end-of-life as part of the normal software development lifecycle, security improvements, and other factors. To support planning for upgrades, this document provides information on upcoming lifecycle changes. While every effort is made to provide sufficient notice of changes, security issues or other factors may occasionally lead to accelerated end-of-life dates.

Lifecycle Stages

To help you plan for end-of-life dates, this page uses the following terms:

  • Deprecated. Feature, component, platform, or functionality that may no longer be efficient or safe. Deprecated features are supported but no longer recommended. Wavefront eventually removes deprecated features. Bug fixes are at Wavefront’s discretion. In particular, Wavefront may require migration to the new feature in lieu of fixing a bug in a deprecated feature. Wavefront identifies deprecated features in the release notes for the release in which the feature is deprecated. For Wavefront proxy, the table below lists deprecated versions.
  • End-of-life. No longer supported. Feature, component, platform, or functionality is no longer supported and may be removed from the product at any time.

Wavefront Proxy

Upgrade to the latest GA release of the Wavefront proxy to get the latest bug fixes and performance enhancements.

The following proxy versions are scheduled to be deprecated or moved to end-of-life.

VersionCurrent StageEnd-of-Life Date
5.x, 6.x, 7.x, 8.x Deprecated TBD
4.x Deprecated Dec 31, 2020
3.24 and lower End-of-Life Jun 30, 2017

Wavefront API

VersionCurrent StageEnd-of-Life Date
2 Active TBD
1 End-of-Life Dec 31, 2017

Delta Counters

Wavefront delta counter behavior changed with Release 2020.26.

  • The original delta counter implementation is now obsolete.
  • The original delta counter implementation is End of Live March 31, 2021.

Required Changes to Delta Counters

As of release 2020.38, any ingested delta counters are stored in both the previous ts() format as well as the new native cs() format.

Starting in April 2021, Wavefront will no longer store delta counters in two different formats, and ts() queries on delta counters will no longer work. You have to revise delta counter queries.

How to Find Queries that Might Need Modification

  1. Find delta counters from the UI or using Spy.
    • From the Wavefront UI, click Browse > Delta Counters and examine your data.
    • From your Web browser, use Delta Counter Spy to view live delta counter ingestion.
  2. Search for any of those named counters on the Alerts page to find relevant Alerts
  3. On the All Dashboards page, use the Metrics Search to find relevant dashboards.

How to Modify the Queries

  1. Replace ts() with cs() if the query targets delta counter data. Filtering works as before, so nothing within the parentheses needs to change.
  2. Remove rate() or ratediff() functions from your delta counter queries.

    Any cs() query tracks the total increments per minute, so cs() data is already a 1 minute rate and doesn’t require the rate() function.

    If you do want to know the per-second rate of change, divide the result by 60.

  3. Remove align() from your delta counter queries.

    cs() data is always minutely aligned and raw or standard aggregations give the same results.


In the following examples, errors.count is a delta counter:

Original QueryNew QueryExplanation
ts(errors.count) cs(errors.count) In the simplest case, just change ts() to cs()
rate(ts(errors.count)) cs(errors.count) / 60 To produce per-second rate of change like the rate() function the cs() divide by 60.
ratediff(ts(errors.count)) cs(errors.count) In the case of ratediff(), no per/second conversion is done. Remove the ratediff() function from the query.

Background: Original and New Delta Counter Implementation

Wavefront delta counters allow you to measure the number of times something occurred over time without needing to keep track of the number of occurrences to date yourself.

At ingestion time, a delta counter must have a ∆ character at the beginning. Just like any other measurement data in Wavefront a delta counter series is uniquely identified by its name, source and any point tags.


For example, imagine we are trying to track the total number of errors that occur across lambda functions running in a given AWS region. Each invocation of the function would measure how many errors occurred during that run and would emit that to Wavefront.

If 5 errors were encountered during a given run, a Lambda running in the us-west-2 region would send: ∆errors.count 5 source=lambda region=us-west-2. Wavefront automatically aggregates any increments received for that same counter allowing you to know the total number of errors that occurred over time, across any number of lambda invocations without any function needing to keep track of that overall state!

Original Implementation

Wavefront originally stored delta values internally as regular metrics emitted every minutes.

For the above example if the data measured across 3 minutes had been a total of: 10 errors in minute 1, 15 errors in minute 2, and 5 errors in minute 3 then if you queried ts(errors.count) for that time range you would see a monotonically increasing count showing 10, 25, 30 across those 3 minutes.

New Implementation

Now we have a new data type specifically for storing delta counters. Data ingestion of delta counters remains unchanged (∆ character indicates delta counter) but the data is now queried via cs() instead of ts(). The original delta counters still report minutely, but instead of maintaining a monotonically increasing count they report the total number of increments that occurred within each minute. In out example, cs(errors.count) displays values of 10, 15, and 5.