WARNING! Gitlab maintenance operation scheduled for Thursday, 18 June between 19:00 and 20:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
@@ -1051,14 +1051,17 @@ Availability and uptime requirements:
-**[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-6]** Managed elements and system nodes and provided services availabilities and statuses shall be tracked and reported.
-**[REQ-METRICS-7a]** Relevant system database and storage health metrics like queries per second, latency and throughput 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 **[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.
When RDPS is used for these functions, the relevant metrics are different and "like queris per second" equivivalent can be used.
Application metrics requirements:
-**[REQ-METRICS-9]** GUI and API latencies and error rates shall be tracked and reported.
@@ -1683,7 +1686,7 @@ There are three different types of assessments used in this document.
#### 6.3.6.7 REQ-METRICS-7
**Requirement a:** Relevant system database and storage health metrics like queries per second, latency and throughput shall be tracked and reported.<br/>
**Requirement a:** Relevant databases in the product and storage health metrics like queries per second, latency and throughput shall be tracked and reported.<br/>
**Requirement b:** Relevant managed element database and storage health metrics like queries per second, latency and throughput shall be tracked and reported.<br/>
**Objective:** Bad service quality can be a indication of compromise.<br/>
