-**[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.
> NOTE: [REQ-MON-2], [REQ-MON-3] and [REQ-MON-4] requirements apply to all collected metrics.
> NOTE: [REQ-MON-1], [REQ-MON-2] and [REQ-MON-3] requirements apply to all collected metrics.
Availability and uptime requirements:
-**[REQ-METRICS-5]** Relevant system and connected element metrics like CPU, memory, disk utilisation shall be tracked and reported.
-**[REQ-METRICS-6a]** System process and service crashes and restarts shall be tracked and reported.
-**[REQ-METRICS-6b]** Managed element process and service crashes and restarts shall be tracked and reported.
-**[REQ-METRICS-7]** Managed elements and system nodes and provided services availabilities and statuses shall be tracked and reported.
-**[REQ-METRICS-8a]** Relevant system database and storage health metrics like queries per second, latency and throughput shall be tracked and reported.
-**[REQ-METRICS-8b]** Relevant managed element database and storage health metrics like queries per second, latency and throughput shall be tracked and reported.
-**[REQ-METRICS-9]** Relevant networking metrics like throughput and protocol errros 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 process and service crashes and restarts shall be tracked and reported.
-**[REQ-METRICS-5b]** Managed element 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-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 errros shall be tracked and reported.
Application metrics requirements:
-**[REQ-METRICS-10]** GUI and API latencies shall be tracked and reported.
-**[REQ-METRICS-11]** GUI and API error rates shall be tracked and reported.
-**[REQ-METRICS-9]** GUI and API latencies shall be tracked and reported.
-**[REQ-METRICS-10]** GUI and API error rates shall be tracked and reported.
Matching tests for these requirements are listed in [6.3.6 Metrics tests].
@@ -931,13 +931,13 @@ For medium risk:
# 6 Conformity assesments and tests
<mark>TODO: make general</mark>
There are three different types of assesments used in this document.
Conceptual assessment, where documentation on the products assets and external access/communication capabilities and claimed authentication mechanisms is compared with the applicability requirement’s text.
**Conceptual assessment**, where documentation on the products assets and external capabilities and claimed mechanisms is compared with the applicability requirement’s text. This style of assesment is kept in minimum.
Functional completeness assessment, Verification that the claimed authentication mechanisms cover all interfaces and functions where authentication is required by the standard and the product’s use case (e.g., are all remote administration functions authenticated?).
**Functional completeness assessment**, where verification that the claimed mechanisms cover all interfaces and functions where the feature is required by the standard and the product’s use case. Often the output is required to show proof of the implementation exactness.
Functional sufficiency assessment, “not necessary of a pure applicability requirement”, it is addressed in the assessment of appropriateness to evaluate whether the authentication mechanisms are adequate for their intended purpose.
**Functional sufficiency assessment**, where it is addressed in the assessment of appropriateness to evaluate whether the requirement implementation is adequate for their intended purpose. This is used with for example system architecture description, where using quantitive metrics would be unreasonable.
