Refined REQ-METRICS-8 and REQ-METRICS-9 objectives

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.

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:

#### 6.3.6.8 REQ-METRICS-8

**Objective:** When the errors stop and the throughput returns to nominal levels, the damage has already been done.<br/>

**Objective:** The error logging records enable for tracing back and serve as entry point for the analysis and detection of abnormal behavior in the managed element and in the system.<br/>

**Preparation:**

1.  Have the product initialised and available with the default configuration and required credentials.

**Activities:**

1. Study the monitoring data GUI.

1. Study the provided documentation to interpret the monitoring data GUI with respect to errors.

1. Study the provided documentation.

1. Generate large amount of traffic in random location.

#### 6.3.6.9 REQ-METRICS-9

**Objective:** Wrong calls to the endpoints is an indication of compromise attempt.<br/>

**Objective:** Response latencies on the product queries or protocol errors on incoming data from managed elements enable to detect defective or compromised managed elements.<br/>

**Preparation:**

1.  Have the product initialised and available with the default configuration and required credentials.