Event Logs: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== VIS Event Logs == | == VIS Event Logs == | ||
A decision based on a detection is called an event and every event is logged by default. An event can be treated as an incident or violation based on values obtained from input channels and rules and conditions implemented in the interpreter. | A decision based on a detection is called an event and every event is logged by default. An event can be treated as an incident or violation based on values obtained from input channels and rules and conditions implemented in the interpreter. | ||
The system separates different events according to their types and records them with video images. '''Video logs''' can be watched via web based user interface. Video logging is optional and can be switched off. | |||
The recording process makes sure that each video starts several frames before the event and ends again several frames after the event concludes. These are called '''pre-'''and '''post-event frames''' and can be configured. Length of the video is configurable and in case a video takes longer than the recording limit, a new video starts where the previous one ends and keeps recording. | |||
Video logs can optionally be sent with '''notification alerts via email''' to specified recipients. Sending can be limited based on input values, such as alerts of events occurring only when the machine is operating. | |||
Each video log contains an '''information section''' on it consisting of the name of the camera, real time IO states, VIS system date and time and running VIS version. | |||
A '''housekeeping''' function makes sure that storage is not overflowing with logs by deleting older records and associated video files when necessary. | |||
[[Category:VIS Features]] | [[Category:VIS Features]] | ||
Revision as of 13:58, 9 July 2025
VIS Event Logs
A decision based on a detection is called an event and every event is logged by default. An event can be treated as an incident or violation based on values obtained from input channels and rules and conditions implemented in the interpreter.
The system separates different events according to their types and records them with video images. Video logs can be watched via web based user interface. Video logging is optional and can be switched off.
The recording process makes sure that each video starts several frames before the event and ends again several frames after the event concludes. These are called pre-and post-event frames and can be configured. Length of the video is configurable and in case a video takes longer than the recording limit, a new video starts where the previous one ends and keeps recording.
Video logs can optionally be sent with notification alerts via email to specified recipients. Sending can be limited based on input values, such as alerts of events occurring only when the machine is operating.
Each video log contains an information section on it consisting of the name of the camera, real time IO states, VIS system date and time and running VIS version.
A housekeeping function makes sure that storage is not overflowing with logs by deleting older records and associated video files when necessary.