Milestone XProtect Advanced VMS 2014 - Manual (Page 144)

Milestone XProtect ® Advanced
VMS 2014
Administrator's Manual
www.milestonesys.com 144 Management Client elements
Event Description
Feed Overflow Started
Feed overflow (media overflow) occurs when a recording server
cannot process received data as quickly as specified in the
configuration and therefore is forced to discard some recordings.
If the server is healthy, feed overflow usually happens because of
slow disk writes. You can resolve this either by reducing the amount
of data written, or by improving the storage system's performance.
Reduce the amount of written data by reducing frame rates,
resolution or image quality on your cameras, but this may degrade
recording quality. If you are not interested in that, instead improve
your storage system's performance by installing extra drives to
share the load or by installing faster disks or controllers.
You can use this event to trigger actions that helps you avoid the
problem, for example, to lower the recording frame rate.
Feed Overflow Stopped
Occurs when feed overflow (see description of the Feed Overflow
Started event) ends.
Live Client Feed Requested
Occurs when client users request a live stream from a device.
The event occurs upon the request even if the client user's request
later turns out to be unsuccessful, for example because the client
user does not have the rights required for viewing the requested live
feed or because the feed is for some reason stopped.
Live Client Feed Terminated
Occurs when client users no longer request a live stream from a
device.
Manual Recording Started
Occurs when a client user starts a recording session for a camera.
The event is triggered even if the device already is being recorded
via rule actions.
Manual Recording Stopped
Occurs when a client user stops a recording session for a camera.
If the rule system also have started a recording session it continues
recording even after the manual recording is stopped.
Marked Data Reference
Requested
Occurs when an evidence lock is made in playback mode in the
clients or via the MIP SDK.
An event is created that you can use in your rules.
Motion Started
Occurs when the system detects motion in video received from
cameras.
This type of event requires that the system's motion detection is
enabled for the cameras to which the event is linked.
In addition to the system's motion detection, some cameras can
detect motion themselves and trigger the Motion Started (HW)
event, but it depends on the configuration of the camera hardware
and in the system. See Hardware - Configurable events above.