Go to documentation repository
Page History
To view the system status data, you need todo the following:
- Go to the web interface of the Selfself-diagnostics Serviceservice: http://127.0.0.1:20041/.
Select the required metric in the list (1) or enter the query in the Expression field.
Expand title Description of useful metrics
SelfMetric
Description
ALERTS_FOR_STATE
Troubleshooting by
Servicethe self-diagnostics
alert name parameterservice.
Code Block title Example ALERTS_FOR_STATE{alertname="ipint_is_not_activated",ep_name="hosts/Server1/DeviceIpint.99",instance="127.0.0.1:20108",job="ngp_export",ngp_alert="true"}
Possible values of the
- Outalertname parameter (see What is the self-diagnostics service):
- low_os_memory
- Camera- — out of RAM;
- ipint_is_not_activated
- No- — camera is connected but does not send data;
- no_samples_in_detector
- the- — no events from a detection tool;
- restart_services_when_archive_source_not_activated
-- — the archive is not working;
- restart_services_when_no_samples_in_archive
with- — recording to archive
- No footage is recorded- with 0 FPS;
- restart_services_when_no_ping_from_detector_to_archive
- — no recording to the archive on detection tool triggering;
- logs_disk_space_is_low
db- /
- Out- db_disk_space_is_low
.- — out of system disk space.
ngp_archive_channel_fps
The frame rate of all video cameras recording to archive
.ngp_cpu_total_usage
The percentage of CPU load on a Server
.ngp_fps
The frame rate of all Server video cameras, all detection tools and their decoders
The request allows for:
Using multiple metrics.
Using expressions to find issuesproblems. For example, a query like ngp_fps <17 will return all metrics, where fps FPS was less than 17. The full For a complete list of logical and arithmetic operators is listed in , see the official Prometheus documentation.
Filtering by any of the parameters. For example, a query like ngp_fps{ep_name=~"hosts/V-BELYAKOV/DeviceIpint.2/SourceEndpoint.video:0:0"} will return fps FPS values only for the specified source.
Examples of useful queries for Windows:
The CPU loading graph similar to the Windows System monitor:Code Block sum by (process_id) (100 / scalar(wmi_cs_logical_processors) * (irate(wmi_process_cpu_time_total{job="os_export", process="AppHost"}[10m]))) or ngp_cpu_total_usage
The graph of RAM usage by the AppHost processes and a total memory space:
Code Block sum by (process_id) (avg_over_time(wmi_process_working_set{job=~"os_export", process="AppHost"}[5m])) / 1024 or avg_over_time(wmi_os_virtual_memory_bytes{job=~"os_export"}[5m]) / 1024
The percentage of RAM usage:
Code Block 100.0 - 100 * avg_over_time(wmi_os_virtual_memory_free_bytes{job=~"os_export"}[5m]) / avg_over_time(wmi_os_virtual_memory_bytes{job=~"os_export"}[5m])
Examples of useful queries for Linux:
The graph of RAM usage by the AppHost processes and a total memory space in bytes:Code Block sum by (groupname) (namedprocess_namegroup_memory_bytes{memtype="resident"})
The percentage of RAM usage:
Code Block 100 - node_memory_MemAvailable_bytes * 100 / node_memory_MemTotal_bytes
The graph of the CPU load by the AppHost processes as a percentage:
Code Block sum by (groupname) (rate(namedprocess_namegroup_cpu_seconds_total[1m])) * 100
The graph of the CPU load as a percentage:
Code Block 100 * avg without (cpu) (1 - rate(node_cpu_seconds_total{mode="idle"}[1m]))
Click the Execute button Click Execute (2).
The Console tab will issue display all possible values of all items elements at the time the request query is completed.When you set a date and time in your calendar, the data will be updated.
To build a graph, go to the Graph tab.
In the field 1, set the time slot interval of the graph, in . In the field 2, set its end point, in . In the filed 3, set the interval between the data points. To fill the chart, select set the stacked (4) checkbox.