Merge pull request SkylineCommunications#691 from MGDSkyline/main

Updated Elecard Documentation

Author: MariekeGO

connector/doc/Elecard_Boro_Monitoring.md

@@ -4,7 +4,9 @@ uid: Connector_help_Elecard_Boro_Monitoring
 
 # Elecard Boro Monitoring
 
-The Elecard Boro Monitoring connector can be used to gather information from the Elecard Boro Solution Server, as well as to create and manage tasks. This connector uses the control API of the Elecard Boro Solution Server to collect the data and send control signals.
+![Elecard Logo.png](~/connector/images/Elecard_Logo.png)
+
+The Elecard Boro Monitoring connector can be used to gather information from the Elecard Boro Solution Server, as well as to create and manage tasks. This connector uses the control API of the Elecard Boro Solution Server to collect data and send control signals.
 
 ## About
 
@@ -61,7 +63,7 @@ On this page, the User ID and Authorization Token From Boro need to be specified
 
 This page also allows you to configure alarms individually for each project. To do so, select a required project in the Project ID field and click the green checkmark to confirm. The project ID/name will then be displayed in the Project ID field.
 
-Except for the Level setting, all **alarm settings** are by default enabled for all projects. You can use the **Level** setting to select an alarm level for a project. This will for instance allow you to configure to receive alarms of Major or Fatal level only.
+Except for the Level setting, all **alarm settings** are enabled for all projects by default. You can use the **Level** setting to select an alarm level for a project. For example, you can configure the Level setting to receive alarms of Major or Fatal level only.
 
 All alarms are selected depending on the general settings configuration. In case, for example, you have only QOE and OTT fields enabled, and the Major level is set, you will receive only QOE and OTT alarms of the Major level.
 
@@ -93,22 +95,22 @@ The **Probe Resources Usage** table displays the following information:
 
 The **Network Interfaces** table displays the probe and interface names, IPV4 and IPV6 addresses, netmask, and transmission/receiving data rates.
 
-### Tasks Pages (IPTV, OTT, SRT, RTMP)
+### Tasks Pages (IPTV, OTT, SRT, RTMP, NDI)
 
-These pages include two tables each, with the live tasks and completed tasks, respectively. The **Completed Tasks Info** table displays all tasks regardless of the protocol.
+These pages include two tables each, with the live tasks and completed tasks, respectively. The **Completed Tasks Info** table displays all tasks, regardless of the protocol.
 
 The tables display the probe name, task name, task state (*Started*, *Stalled*, etc.), protocol (*HLS*, *DASH*, *IPTV*, etc.), URI, task start time, interface name, and streaming interface. In addition, the **Node Type** column shows whether the task is independent (i.e. it does not contain subtasks — SINGLE or ROOT) or it has subtasks (ROOT, CHILD). You can stop or resume tasks with the **Action** field.
 
 ### Active Alarms Page
 
 This page includes a table with active alarms and a table with completed alarms.
 
-Both tables display the project title, probe name, and task name. They also contain information about the task URI, alarm level (*OK*, *error*, *warning*, *major*, or *fatal*), alarm start time, and alarm group (ETH - Ethernet, ETR - TR 101 290, QOE - Quality of experience, OTT - OTT and Progressive Download,  or SYS - System и SCTE35).
+Both tables display the project title, probe name, and task name. They also contain information about the task URI, alarm level (*OK*, *error*, *warning*, *major*, or *fatal*), alarm start time, and alarm group (ETH — Ethernet, ETR — TR 101 290, QOE — Quality of Experience, OTT — OTT and Progressive Download, or SYS — System and SCTE35).
 
 ### Start Task Page
 
-This page is designed for a task creation. It displays a form that allows you to create a task in the same way as in the Boro Solution Server web UI. To create a task, fill in the appropriate fields. First select a **Project ID**, then a **Probe ID**, and then the **Interface**. When you make your selection, always click the green checkmark for the corresponding field to confirm.
+This page is designed for task creation. It displays a form that allows you to create a task in the same way as in the Boro Solution Server web UI. To create a task, fill in the appropriate fields. First, select a **Project ID**, then a **Probe ID**, and then an **Interface**. When you make your selection, always click the green checkmark for the corresponding field to confirm.
 
 The Project ID is taken from the projects table. The Probe ID field is filtered by the connector depending on the selected project. This way, only probes belonging to the project with the selected ID are available. Interfaces are filtered by the protocol depending on the selected probe.
 
-Some settings can be selected from a list, while others should be specified manually. Each time, you need to click the green checkmark to save your settings. When all settings have been configured, click the **Start Task** button to run a task.
+Some settings can be selected from a list, while others should be specified manually. Each time, you need to click the green checkmark to save your settings. When all settings have been configured, click the **Start Task** button to run the task.