On the Alarms and Events tab, you can specify settings for alarms, events and logs.
Name |
Description |
|
---|---|---|
Keep closed alarms for |
Specify the number of days for storing alarms with the state Closed in the database. If you set the value to 0, the alarm is deleted after it has been closed. Alarms always have timestamps. If the alarm is triggered by a camera, the timestamp has an image from the time of the alarm. The alarm information itself is stored on the event server, while the video recordings corresponding to the attached image are stored on the relevant surveillance system server. |
|
Keep all other alarms for |
Specify the number of days for storing alarms with the state New, In progress, or On hold. If you set the value to 0, the alarm appears in the system, but will not be stored. Alarms always have timestamps. If the alarm is triggered by a camera, the timestamp has an image from the time of the alarm. The alarm information itself is stored on the event server, while the video recordings corresponding to the attached image are stored on the relevant surveillance system server. |
|
Keep logs for |
Specify the number of days for keeping the event server logs. If you keep the logs for longer periods of time, ensure that the machine where the event server is installed has enough disk space. |
|
Enable verbose logging |
To keep a more detailed log for event server communication, select the check box. It will be stored for the number of days specified in the Keep logs for field. |
|
Event types |
Specify the number of days for storing events in the database. There are two ways of doing this:
If the value is 0, the events will not be stored in the database. The external events (user-defined events, generic events, and input events) are set to 0 by default, and you cannot change that value. The reason is that these types of events occur so frequently that storing them in the database may cause performance issues. |
© 2018 Milestone Systems A/S