Jump to content

System Logs

From Event Gates Wiki

System Logs

A set of system activities are logged for reviewing and management purposes. Some of these values are also logged in every system start-up. Mute logs which are triggered when the mute is turned on or off can be associated with an email alert.

Logs on startup

Some of the system information is always logged on every startup. See description column in below recorded logs table for startup_log.

Email notifications

VIS is capable of sending notification emails to registered recipients for specific events:

More events may be added during the course of the time. (Available with V26)

Text and recipients of the alerts are stored in configuration files and updated with Configuration Manager.

Housekeeping

Viewing Logs

List of logs

These are the items logged related to the system events.

Log Type Event Event Id Desc Status
System Camera added 101 Added before 22.1886.1425
Removed in 25.2084.0950 Camera can't be added in Visor UI
Cancelled
System Camera removed 102 Added before 22.1886.1425
Removed in 25.2084.0950 Camera can't be removed in Visor UI
Cancelled
System Camera modified 103 Added before 22.1886.1425
Removed in 25.2084.0950
Camera can't be modified in Visor UI
Cancelled
System Housekeeping removed logs 104 Implemented in V26. When housekeeping ran and removed some logs and videos. Both numbers should be logged. Active
System HB down 105 Implemented in V26. Active
System HB resumed 106 Implemented in V26. Active
System Camera feed lost 107 Implemented in V26. startup_log Active
System Camera resumed 108 Implemented in V26. startup_log Active
System IPIO connection lost 109 Implemented in V26. startup_log Active
System IPIO connection resumed 110 Implemented in V26. startup_log Active
System VIS started 111 Implemented in V26. startup_log Active
System GPU Temp - normal 112 Implemented in V26. VIS controls GPU temp once every minute and logs if state change detected from overheat to normal and once at start up if started at normal temperature. startup_log Active
System GPU Temp - overheat 113 Implemented in V26. VIS controls GPU temp once every minute and logs if state change is detected to overheat and once at start up if started at overheat temperature. startup_log Active
System Mute on 114 Implemented in V26. VIS is notified by the IO to mute or that the IO itself is muted. startup_log Active
System Mute off 115 Implemented in V26. startup_log Active
System Internet connection lost 116 Implemented in V26. If there was an i̇nternet connection. startup_log Active
System Internet connection established 117 Implemented in V26. Once VIS connects to the i̇nternet. startup_log Active
System Camera view tempered 118 Camera angle changed, blurred, blocked. TBD TBD
System Region modified 119 Implemented in V26. Active
System Exceptions 120 Unknown exception. TBD TBD
System VIS shutdown 121 Implemented in V26. Active
System Model changed 122 Implemented in V26. From file modification of .trt. startup_log Active
System VIS codebase changed 123 TBD TBD
System VIS interpreter changed 124 TBD TBD
System VIS started with modified version 125 unsigned VIS, TBD TBD
System RSC Recorded 126 Implemented in V26 SP1. When the RSC is done recording a downloadable zip will be available in the logs. Active
System User logs in TBD TBD see FR-0043 TBD
System Users download video TBD TBD see FR-0044 TBD

Notes

  1. ↑ If the mute_input is set in the IO configuration, when the HIGH signal is received from that input pin, VIS sends an email to the mute recipients list that is defined in vis.yaml. Mute alert is sent with the IPIO display_name field that is set in IO configuration. If the mute_input is set to anything other than the input numbers available on IPIO, namely one through four, mute alert is disabled.