@@ -1059,17 +1059,17 @@ The **[REQ-METRICS-5]** is vague by design.
The product can host an ecosystem that exposes managed elements capacity for 3rd. party applications.
The product then operates as a runtime for the workload, and needs to inherit operating system responsibilies.
The **[REQ-METRICS-7*]** is defined expecting that the product hosts these services.
The **[REQ-METRICS-7\*]** is defined expecting that the product hosts these services.
When RDPS is used for these functions, the relevant metrics are different and "like queris per second" equivivalent can be used.
The **[REQ-METRICS-8]** and **[REQ-METRICS-9]** below can refer either the product or the connected devices. Relevancy of the metric depends on the protocols and the product usage scenario.
Application metrics requirements:
-**[REQ-METRICS-9]** GUI and API latencies and error rates shall be tracked and reported.
Matching tests for these requirements are listed in [6.3.6 Metrics tests].
[6.3.6 Metrics tests].: #636-metrics-tests
### 5.3.7 Data minimisation
These requirements are generally binding, and there is no low-medium-high tiering available.
