Skip to main content

Cumulativetodelta Processor

Status Available in: contrib, k8s Maintainers: @TylerHelmuth Source: opentelemetry-collector-contrib

Supported Telemetry

Metrics

Overview

Configuration

Configuration is specified through a list of metrics. The processor uses metric names to identify a set of cumulative metrics and converts them from cumulative to delta. The following settings can be optionally configured:
  • include: List of metrics names (case-insensitive), patterns or metric types to convert to delta. Valid values for metric types are: sum, histogram, exponentialhistogram.
  • exclude: List of metrics names (case-insensitive), patterns or metric types to not convert to delta. If a metric name matches both include and exclude, exclude takes precedence. Valid values for metric types are: sum, histogram, exponentialhistogram.
  • max_staleness: The total time a state entry will live past the time it was last seen. Set to 0 to retain state indefinitely. Default: 1 hour
  • initial_value: Handling of the first observed point for a given metric identity. When the collector (re)starts, there’s no record of how much of a given cumulative counter has already been converted to delta values.
    • auto (default): Send if and only if the startime is set AND the starttime happens after the component started AND the starttime is different from the timestamp. Suitable for gateway deployments, this heuristic is like drop, but keeps values for newly started counters (which could not have had previous observed values).
    • keep: Send the observed value as the delta value. Suitable for when the incoming metrics have not been observed before, e.g. running the collector as a sidecar, the collector lifecycle is tied to the metric source.
    • drop: Keep the observed value but don’t send. Suitable for gateway deployments, guarantees that all delta counts it produces haven’t been observed before, but loses the values between thir first 2 observations.
If neither include nor exclude are supplied, no filtering is applied.

Examples

Troubleshooting

When Telemetry is enabled, this component can export several metrics. All metrics are disabled by default and must be opted-in via the collector’s service.telemetry.metrics.level configuration.

Warnings

  • Statefulness: The cumulative_to_delta processor’s calculates delta by remembering the previous value of a metric. For this reason, the calculation is only accurate if the metric is continuously sent to the same instance of the collector. As a result, the cumulative_to_delta processor may not work as expected if used in a deployment of multiple collectors. When using this processor it is best for the data source to being sending data to a single collector.

Attributes

Configuration

Example Configuration


Last generated: 2026-08-24