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.
    

   Expand
   title  Description of useful metrics
   Metric Description ALERTS_FOR_STATE Troubleshooting by 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_ export exporter",ngp_alert="true"} Possible values of the alert name parameter: 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 footage is recorded on detection; 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_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:

   1. Using multiple metrics.

   2. Using expressions to find issues. For example, a query like ngp_fps <17 will return all metrics where fps was less than 17. The full list of logical and arithmetic operators is listed in the official Prometheus documentation.  

   3. Filtering by any of the parameters. For example, a query like ngp_fps{ep_name=~"hosts/VR-BELYAKOVPROKOFIEV/DeviceIpint.2/SourceEndpoint.video:0:0"} will return fps values only for the specified source.
      
      Examples of useful queries:
      CPU load shedule by analogy with the Windows System Monitor:

      Code Block
      sum by (process_id) (100 / scalar(wmi_cs_logical_processors) * (irate(wmi_process_cpu_time_total{job="os_exporter", process="AppHost"}[10m]))) or ngp_cpu_total_usage

      The shedule of RAM usage by AppHost processes and the total amount of memory:

      Code Block
      sum by (process_id) (avg_over_time(wmi_process_working_set{job=~"os_exporter", process="AppHost"}[5m])) or avg_over_time(wmi_os_virtual_memory_bytes{job=~"os_exporter"}[5m])

      Percentage of RAM usage:

      Code Block
      100.0 - 100 * avg_over_time(wmi_os_virtual_memory_free_bytes{job=~"os_exporter"}[5m]) / avg_over_time(wmi_os_virtual_memory_bytes{job=~"os_exporter"}[5m])

      
      

3. Click  Execute (2).
   The Console tab will issue all possible values of all items at the time the request is completed.
   Image Modified
   

4. When you set a date and time in your calendar, the data will be updated.
   
   

5. To build a graph, go to the Graph tab.
   Image Modified
   In field 1, set the time slot of the graph, in field 2 set its end point, in filed 3 set the interval between data points. To fill the chart, select the stacked (4) checkbox.