Documentation

Work with Prometheus counters

Use Flux to query and transform Prometheus counter metrics stored in InfluxDB.

A counter is a cumulative metric that represents a single monotonically increasing counter whose value can only increase or be reset to zero on restart.

Prometheus metric types

Example counter metric in Prometheus format
# HELP example_counter_total Total representing an example counter metric
# TYPE example_counter_total counter
example_counter_total 282327

Because counters can periodically reset to 0, any query involving counter metrics should normalize the data to account for counter resets before further processing.

The examples below include example data collected from the InfluxDB OSS 2.x /metrics endpoint using prometheus.scrape() and stored in InfluxDB.

Prometheus metric parsing formats

Query structure depends on the Prometheus metric parsing format used to scrape the Prometheus metrics. Select the appropriate metric format version below.

Normalize counter resets

  1. Filter results by the prometheus measurement and counter metric name field.
  2. Use increase() to normalize counter resets. increase() returns the cumulative sum of positive changes in column values.

increase() accounts for counter resets, but may lose some precision on reset depending on your scrape interval. On counter reset, increase() assumes no increase.

from(bucket: "example-bucket")
    |> range(start: -1m)
    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "http_query_request_bytes")
    |> increase()
Raw Prometheus counter metric in InfluxDB
Increase on Prometheus counter metric in InfluxDB

View example input and output data

  1. Filter results by the counter metric name measurement and counter field.
  2. Use increase() to normalize counter resets. increase() returns the cumulative sum of positive changes in column values.

increase() accounts for counter resets, but may lose some precision on reset depending on your scrape interval. On counter reset, increase() assumes no increase.

from(bucket: "example-bucket")
    |> range(start: -1m)
    |> filter(fn: (r) => r._measurement == "http_query_request_bytes" and r._field == "counter")
    |> increase()
Raw Prometheus counter metric in InfluxDB
Increase on Prometheus counter metric in InfluxDB

View example input and output data

Calculate changes between normalized counter values

Use difference() with normalized counter data to return the difference between subsequent values.

from(bucket: "example-bucket")
    |> range(start: -1m)
    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "http_query_request_bytes")
    |> increase()
    |> difference()
Raw Prometheus counter metric in InfluxDB
Normalize Prometheus counter metric to account for counter resets

View example input and output data

from(bucket: "example-bucket")
    |> range(start: -1m)
    |> filter(fn: (r) => r._measurement == "http_query_request_bytes" and r._field == "counter")
    |> increase()
    |> difference()
Raw Prometheus counter metric in InfluxDB
Normalize Prometheus counter metric to account for counter resets

View example input and output data

Calculate the rate of change in normalized counter values

Use derivative() to calculate the rate of change between normalized counter values. By default, derivative() returns the rate of change per second. Use the unit parameter to customize the rate unit.

from(bucket: "example-bucket")
    |> range(start: -1m)
    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "http_query_request_bytes")
    |> increase()
    |> derivative()
Normalized Prometheus counter metric in InfluxDB
Calculate the rate of change in Prometheus counter metric with Flux

View example input and output data

from(bucket: "example-bucket")
    |> range(start: -1m)
    |> filter(fn: (r) => r._measurement == "http_query_request_bytes" and r._field == "counter")
    |> increase()
    |> derivative()
Normalized Prometheus counter metric in InfluxDB
Calculate the rate of change in Prometheus counter metric with Flux

View example input and output data

Calculate the average rate of change in specified time windows

To calculate the average rate of change in normalized counter values in specified time windows:

  1. Import the experimental/aggregate package.

  2. Normalized counter values.

  3. Use aggregate.rate() to calculate the average rate of change per time window.

    • Use the every parameter to define the time window interval.
    • Use the unit parameter to customize the rate unit.By default, aggregate.rate() returns the per second (1s) rate of change.
    • Use the groupColumns parameter to specify columns to group by when performing the aggregation.
import "experimental/aggregate"

from(bucket: "example-bucket")
    |> range(start: -1m)
    |> filter(fn: (r) => r._measurement == "prometheus" and r._field == "http_query_request_bytes")
    |> increase()
    |> aggregate.rate(every: 15s, unit: 1s)
Normalized Prometheus counter metric in InfluxDB
Calculate the rate of change in Prometheus counter metrics per time window with Flux

View example input and output data

import "experimental/aggregate"

from(bucket: "example-bucket")
    |> range(start: -1m)
    |> filter(fn: (r) => r._measurement == "http_query_request_bytes" and r._field == "counter")
    |> increase()
    |> aggregate.rate(every: 15s, unit: 1s)
Normalized Prometheus counter metric in InfluxDB
Calculate the rate of change in Prometheus counter metrics per time window with Flux

View example input and output data


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2