Convert cumulative OTel Collector metrics to delta temporality with the cumulativetodelta processor

domain: github.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Add a `cumulativetodelta` processor to the Collector config
  2. Use `include`/`exclude` with `metrics` (names/regex) and/or `metric_types` (sum, histogram, exponentialhistogram) to scope which series convert
  3. Set `max_staleness` to bound how long a series' state is retained (default 1h; 0 disables staleness eviction)
  4. Set `initial_value` (`auto`, `keep`, or `drop`) to control handling of the first data point per series
  5. Place the processor in the metrics pipeline ahead of an exporter that requires delta temporality
  6. Deploy and verify downstream metrics arrive as deltas

Known gotchas

Related routes

Configure OTel metrics SDK for delta vs cumulative temporality per exporter
opentelemetry.io · 5 steps · unrated
Configure cardinality control in an OTel Collector metrics pipeline using the metricstransform processor and the transform processor to aggregate away high-cardinality dimensions
opentelemetry.io · 5 steps · unrated
Configure an exponential histogram in the OTel SDK and Collector for high-resolution latency distribution without manual bucket tuning
opentelemetry.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans