Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read and how they find the site, so we can improve it (Google Analytics).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors
22.5k Try for free

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

Telemetry Aggregation

Every field added to a Trendz view has an aggregation type that controls how raw telemetry is reduced to a single value per time bucket or group. Choose the aggregation that matches the meaning of the measurement.

Type Description
AVG Arithmetic mean of all values in the group.
SUM Total sum of all values in the group.
MIN Smallest value in the group.
MAX Largest value in the group.
LATEST Most recent value recorded in the group’s time range.
COUNT Number of data points in the group.
UNIQ Number of distinct values in the group.

To change the aggregation type, click the field in the view configuration panel and select the required value.

Some devices report a monotonically increasing counter — a pulse output — rather than an instantaneous reading. A water meter, electricity meter, or gas meter are typical examples: the raw value always grows and the meaningful metric is consumption over a period, not the absolute counter.

Raw pulse counter (always increasing):
time ──────────────────────────────────────▶
value 100 150 210 290 310 400
Delta per interval (consumption):
time ──────────────────────────────────────▶
value 50 60 80 20 90

Select DELTA aggregation for such a field and Trendz will automatically compute the consumption for each time bucket at the chosen granularity.

When DELTA is applied to a field that spans multiple devices (for example, all water meters in a building), Trendz computes the delta for each device individually and then applies SUM to combine them. The result is the total consumption at any level of your topology — city, building, floor, or apartment.

Building (query result after DELTA + SUM):
┌─────────────────────────────────────────────┐
│ Building A — total consumption: 230 L │
└──────────────┬──────────────────────────────┘
│
┌─────────┴──────────┐
▼ ▼
┌─────────────┐ ┌─────────────┐
│ Meter 1 │ │ Meter 2 │
│ delta: 90 │ │ delta: 140 │
└─────────────┘ └─────────────┘
SUM → 230