Learn when and how to use delta counters.

Wavefront supports several types of metrics. Counters are useful for aggregating metric information such as the number of hits on a web page, how many users log into a portal, etc. Delta counters make counter functionality available for serverless Function-as-a-service environments and some other use cases.

For example, users who are monitoring an environment where multiple sources perform the same function can’t use regular counters. Lost points because of collision are likely. Wavefront solves the problem by performing the aggregation on the server side.

Where Are Delta Counters Useful?

Delta counters are useful if you want to combine points that come in at the same time from several sources. For example:

  • You’re monitoring a Function-as-a-Service (FaaS or serverless) environment, and many functions execute simultaneously. It’s not possible to monitor bursty traffic like that without losing some reported metric points due to collision.
  • You want to collect metrics from two sets of applications, each using a separate Telegraf instance behind a load balancer. telegraf and delta_counters
  • You want to aggregate counters across multiple apps. For example, Wavefront uses delta counters for the logs to metrics Wavefront integration.

For more on delta counter use cases, see our blog Monitoring Apps in the Serverless World: Introducing Wavefront Delta Counters

Collecting Counter Metrics and Delta Counter Metrics

Even in a serverless environment, it makes sense to collect both counter metrics and delta counter metrics.

  • Use regular counters for monitoring over long periods of time, where a small number of metrics lost to collision are not a problem.
  • Use delta counters to accurately accumulate points when shorts bursts of high-volume traffic is experienced and collisions can become a problem.

Example: Monitoring AWS Lambda

AWS Lambda allows you to specify functions that you want to run – and then you can stop worrying about the function execution. For example, assume that you want to generate a thumbnail each time any of your users uploads images to a folder. You can write a Lambda function that monitors the folders and takes care of thumbnail generation for you. AWS runs as many of the functions as necessary to handle the current workload, and you don’t have to worry about scaling up or down.

Delta counters make monitoring easy for this use case. The Wavefront service aggregates the metrics that come from different invocations of the same function. The Wavefront AWS Lambda Functions integration comes preconfigured with several delta counters and a gauge for standard metrics. In addition, you can monitor custom business metrics by using our SDK to define a wrapper for your AWS Lambda function. See the AWS Lambda Functions Integration for setup instructions.

Using Delta Counters

To use delta counters, you have several options:

  • Start with our sample libraries.
  • Send metrics as delta counters explicitly by specifying a delta character as the first letter of the metric name.

Delta Counter Proxy Configuration Properties

We support the following proxy configuration properties with delta counters.

  • deltaCounterPorts: Comma-separated list of ports that accept only delta counter data.
  • deltaCounterAggregationInterval: Time that the proxy spends aggregating data before sending them to the Wavefront Service. Default is 30 seconds.


You can use our SDKs to make your metric a delta counter.

AWS Lambda SDKs - These AWS Lambda wrappers illustrate how to use delta counters:

Python Client - For an example of using delta counters without an integration, see the delta.py file, which is part of the wavefront_pyformance module.

Delta Prefix

If you want to send metrics as delta counters to the Wavefront proxy or directly to the Wavefront service, you must prefix each metric with a delta (∆) character, as shown in the following sample code snippet.

DELTA_PREFIX = u"\u2206"
ALT_DELTA_PREFIX = u"\u0394"

Best Practices

Delta counters are like other counters in many ways.

  • You can apply query language functions such as rate() to a delta counter.
  • You can create alerts that use delta counters in the condition, for example, to monitor whether the counter goes beyond a certain threshold.

Delta counters have some special characeristics.

  • The timestamp of a delta counter is the time at which the point was aggregated by the Wavefront service. For regular counters, the timestamp is the time when the point is emitted.
  • If the source for your delta counters stops reporting, Wavefront continues reporting once a minute for 1 hour. If the source does not report for an hour, Wavefront resets the delta counter to 0, stops aggregating, and stops reporting.