Only few events that are registered on the Siveillance video are received by the Activity Feed node in Rule Editor. Some of those events are described in the following sections.

 

User Defined Events

Some of the User Defined Events (UDE) are listed below.

  • UDE name as defined in Siveillance Video
  • Date/time stamps

 

Video Source State Change

Every time the status of a connected video source changes, Rule Editor receives some of the following data:

  • DeviceName for example, Axis 233D Camera (Ip address) - Camera 1
  • Date/Time stamp
  • Previous State for example, ErrorSignalLost that means the video stream is not available on the recording server.
  • Current State: Some of the examples of current state are listed below:
    • ErrorSignalLost: The video stream is not available on the recording server.
    • ErrorNoConnection: Loss of network communication with VMS.
    • ok: Health status of the VMS device.
    • Disabled: Video source is disabled.

 

Recording Status State Change

When the recording status of the connected video source changes, Rule Editor receives some of the following data:

  • DeviceName for example, Axis 233D Camera (IP address) - Camera 1
  • Date/Time stamp
  • Current State: Some of the examples are listed below:
    • Stopped: Recording has stopped.
    • Recording: Recording is on.
    • Unknown: Recording status is unknown. This message is received when the device is in transition mode.

 

NVR Node Status Change

When the status of the recording server, also known as NVR node changes, Rule Editor receives some of the following data:

  • Server name for example, EC2AMAZ-P5BS1MR
  • Date/Time stamp
  • Current State: Some of the examples are listed below:
    • Stopped: The VMS recording server has stopped.
    • Running: The VMS recording server is up and running.

 

System Monitoring Threshold

Rule Editor receives data according to the criteria defined under the System Monitoring Thresholds in the configuration client. The system threshold events can be either server specific or camera specific.

Server Specific Threshold Events

  • Server name for example, EC2AMAZ-P5BS1MR
  • Date/Time stamp
  • Name of the event for example,
    • CPU Usage Normal
    • CPU Usage Warning
    • CPU Usage Critical
    • Retention Time Critical
    • Retention Time Warning
    • Retention Time Normal
    • Memory Usage Normal
    • Memory Usage Warning
    • Memory Usage Critical
    • Free Space Normal
    • Free Space Warning
    • Free Space Critical
    • NVIDIA decoding Normal
    • NVIDIA decoding Warning
    • NVIDIA decoding Critical
    • NVIDIA memory Normal
    • NVIDIA memory Warning
    • NVIDIA memory Critical

Camera Specific Threshold Events

  • Camera name for example, DirectShow Virtual Video Server (IP address) - Camera 3
  • Date/Time stamp
  • Name of the event for example,
    • Live FPS Normal
    • Live FPS Warning
    • Live FPS Critical
    • Recording FPS Normal
    • Recording FPS Critical
    • Recording FPS Warning
    • Used Space Normal
    • Used Space Warning
    • Used Space Critical