You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Define the path to the entities from which the data will be read for aggregation, as well as the relationship type between the target entity and the related entities.
43
43
'
44
44
%}
@@ -61,7 +61,7 @@ For more details about arguments and configuration, see the [Arguments](/docs/us
title: Click **Add argument** (1) and fill in the required fields:<br>select the **Argument type** (2), specify the **Time series key / Attribute key** (3) to read data from, enter the **Argument name** (4) that will be used in the metrics, and set the **Default value** (5).<br>Then click **Add** (6).”
66
66
'
67
67
%}
@@ -93,7 +93,7 @@ return temperature > 10 && status == "active";
title: Click **Add metric** (1) and configure the following:<br>specify the **metric name** (2), select the **aggregation type** (3), optionally enable a **filter** (4), choose the **value source** (Key or Function) (5), and enter the **argument name** (6) that will be used as the data source.<br>Then click **Add** (7).
98
98
'
99
99
%}
@@ -115,7 +115,7 @@ This prevents excessive reprocessing and reduces system load in high-frequency e
title: **Deduplication interval** is the minimum time period between repeated aggregations. It limits how often a calculated field can re-aggregate data from related entities in response to frequent updates.
title: Create relationships between Building A and all smart sensors: Relationship direction: From (Devices ⇾ Building A); Relationship type: Manages
title: Apply the calculated field to the **building** asset profile.<br>Propagation path to related entities: **Relation direction**: Down to child; **Relation type**: Manages.
title: The Building A asset stores the aggregated telemetry values, such as:<br>- **avgTemperature** — average temperature across all sensors<br>- **maxTemperature** — maximum temperature measured by one of the sensors
title: Click **Add argument** (1) and fill in the required fields:<br>- **Time series key** (2) — the telemetry key whose data will be aggregated (for example, temperature, power, voltage)<br>- **Argument name** (3) — the variable name referenced by metrics.<br>Then click **Add** (4).
40
40
'
41
41
%}
@@ -58,7 +58,7 @@ Click the **Add metric** button and fill in the required fields:
title: Click the **Add metric** button (1) and fill in the required fields:<br>- **Metric name** (2): output telemetry key name (e.g., tempAvg, tempMax)<br>- **Aggregation** (3): Average / Min / Max / Sum / Count<br>- **Argument name** (4): the argument whose value is being aggregated.<br>- **Default value** (5): used if the interval contains no data<br>Then click **Add** (6).
63
63
'
64
64
%}
@@ -76,7 +76,7 @@ Example: **every 1 hour** produces results at 00:00, 01:00, 02:00, etc.
title: Aggregation interval: Hour; Time zone: use your reporting time zone.<br>The computed values are stored as telemetry (time series) keys.<br>Click **Add** to save the calculation field.
237
237
'
238
238
%}
@@ -259,7 +259,7 @@ Example output for one interval:
title: On the **Energy Meter 1** device, the aggregated values are stored as telemetry (time series) keys:<br>- **powerHourlyAvg** — hourly average power usage<br>- **powerHourlyMax** — hourly peak power usage<br>- **energyHourlySum** — hourly energy consumption
0 commit comments