Page History

...

1. Go to the web interface of the self-diagnostics service: http://127.0.0.1:20040/.
   

2. Select the required metric in the list (1) or enter the query in the Expression field.
   

   Metric	Description
   ALERTS_FOR_STATE	Troubleshooting by the self-diagnostics service. 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_exporter",ngp_alert="true"} Possible values of the alertname parameter (see General information about the self-diagnostics service): low_os_memory—out of RAM; ipint_is_not_activated—camera is connected, but does not send data; no_samples_in_detector—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—recording to archive with 0 FPS; restart_services_when_no_ping_from_detector_to_archive—no recording to the archive of an event from a detection tool; logs_disk_space_is_low/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_archive_volume_size	The current size of the archive

   volume

   in bytes
   ngp_cpu_total_usage	The percentage of CPU load on a Server
   ngp_fps	The frame rate of all Server cameras, all detection tools and their decoders

   The request allows for:

   1. Using multiple metrics.

   2. Using expressions to find problems. For example, a query like ngp_fps <17 will return all metrics, where FPS is less than 17. For a complete list of logical and arithmetic operators, see the official Prometheus documentation.  

   3. Filtering by any of the parameters. For example, this query will return FPS values only for the specified source:

      Code Block
      ngp_fps{ep_name=~"hosts/TEST/DeviceIpint.2/SourceEndpoint.video:0:0"}

3. Click on the Execute button (2).

...