@@ -475,23 +475,24 @@ These requirements are generally binding, and there is no low-medium-high tierin
General requirements:
-**[REQ-METRICS-0]** The product shall be designed in a way that collected and stored metrics data can not be altered.
-**[REQ-METRICS-1]** Historical metrics data import overwriting an existing data point shall be noticed.
-**[REQ-METRICS-2]** Metrics name, purpose, and value interpretation shall be described for the user.
-**[REQ-METRICS-3]** Metrics cadence, accuracy and storage time shall be described for the user.
***[REQ-METRICS-0]** The product shall be designed in a way that collected and stored metrics data can not be altered.
***[REQ-METRICS-1]** Historical metrics data import overwriting an existing data point shall be noticed.
***[REQ-METRICS-2]** Metrics name, purpose, and value interpretation shall be described for the user.
***[REQ-METRICS-3]** Metrics cadence, accuracy and storage time shall be described for the user.
***[REQ-METRICS-9]** The product shall not collect data unrelated to the purpose of the product operation.
> NOTE: [REQ-METRICS-1], [REQ-METRICS-2] and [REQ-METRICS-3] requirements apply to all collected metrics.
Availability and uptime requirements:
-**[REQ-METRICS-4]** Relevant system and connected element metrics like CPU, memory, disk utilisation shall be tracked and reported.
-**[REQ-METRICS-5a]** System incidents, such as process and service crashes and restarts, shall be tracked and reported.
-**[REQ-METRICS-5b]** Managed element incidents, such as process and service crashes and restarts shall be tracked and reported.
-**[REQ-METRICS-6a]** Managed elements availabilities and statuses shall be tracked and reported.
-**[REQ-METRICS-6b]** System and provided service availabilities and statuses shall be tracked and reported.
-**[REQ-METRICS-7a]** Relevant databases in the product and storage health metrics like queries per second, latency and throughput shall be tracked and reported.
-**[REQ-METRICS-7b]** Relevant managed element database and storage health metrics like queries per second, latency and throughput shall be tracked and reported.
-**[REQ-METRICS-8]** Relevant networking metrics like throughput and protocol errors shall be tracked and reported.
***[REQ-METRICS-4]** Relevant system and connected element metrics like CPU, memory, disk utilisation shall be tracked and reported.
***[REQ-METRICS-5a]** System incidents, such as process and service crashes and restarts, shall be tracked and reported.
***[REQ-METRICS-5b]** Managed element incidents, such as process and service crashes and restarts shall be tracked and reported.
***[REQ-METRICS-6a]** Managed elements availabilities and statuses shall be tracked and reported.
***[REQ-METRICS-6b]** System and provided service availabilities and statuses shall be tracked and reported.
***[REQ-METRICS-7a]** Relevant databases in the product and storage health metrics like queries per second, latency and throughput shall be tracked and reported.
***[REQ-METRICS-7b]** Relevant managed element database and storage health metrics like queries per second, latency and throughput shall be tracked and reported.
***[REQ-METRICS-8]** Relevant networking metrics like throughput and protocol errors shall be tracked and reported.
The **[REQ-METRICS-5]** is vague by design.
The product can host an ecosystem that exposes managed elements capacity for 3rd. party applications.
