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
Copy file name to clipboardExpand all lines: _includes/docs/paas/subscription.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -687,17 +687,16 @@ See product [homepage](/products/trendz/){:target="_blank"} for more details.
687
687
688
688
## How to cancel my subscription?
689
689
690
-
To terminate your ThingsBoard Cloud subscription, follow these steps:
690
+
To cancel your ThingsBoars {{cloudPrefix}} Cloud subscription, follow these steps:
691
691
692
-
- Log in to ThingsBoard Cloud as Tenant Administrator;
693
-
- Navigate to the "**Plan and billing**" page in the main navigation menu;
694
-
- Locate the **Management** section, which contains your subscription details and options to control it;
695
-
- Click the "**Cancel subscription**" button and follow the instructions to cancel your subscription;
696
-
- Confirm the action by clicking the "**Cancel subscription**" button in the confirmation window.
692
+
- Navigate to **Plan and billing**.
693
+
- Click **Cancel subscription**.
694
+
- Follow the on-screen instructions.
695
+
- Confirm the cancellation by clicking **Cancel subscription** in the confirmation dialog.
697
696
698
-
{% capture difference %}
697
+
{% capture update-only-keys-cluster-mode %}
699
698
**Note:**
700
699
<br>
701
700
This action cannot be undone. This will **permanently delete** your tenant account, all devices, assets, dashboards, rule-chains, users and other entities, all telemetry data and alarms.
702
701
{% endcapture %}
703
-
{% include templates/info-banner.md content=difference %}
702
+
{% include templates/warn-banner.md content=update-only-keys-cluster-mode %}
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
%}
@@ -109,13 +109,13 @@ How it works:
109
109
- additional updates arriving within the interval do not trigger aggregation again
110
110
- after the interval ends, aggregation run again using the latest available data
111
111
112
-
> Minimum time between telemetry aggregations: 60 seconds.
112
+
> Minimum time between telemetry aggregations: 10 seconds.
113
113
114
114
This prevents excessive reprocessing and reduces system load in high-frequency environments.
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
%}
@@ -50,16 +50,16 @@ Each metric produces **one output telemetry key (Metric name)** by applying one
50
50
51
51
Click the **Add metric** button and fill in the required fields:
52
52
-**Metric name**: output telemetry key name (e.g., tempAvg, tempMax)
53
-
-**Aggregation**: Average / Min / Max / Sum / Count / Count unique
53
+
-**Aggregation**: Average / Min / Max / Sum / Count
54
54
-**Argument name**: the argument whose value is being aggregated.
55
55
-**Default value**: used if the interval contains no data
56
56
57
57
> You can create multiple metrics from the same argument (e.g., <spanclass="code-light">tempAvg</span>, <spanclass="code-light">tempMin</span>, <spanclass="code-light">tempMax</span>).
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 / Count unique<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).
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
%}
65
65
@@ -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