Event Management
Effective from Doors.NET v_3.5.1.22, historical event information is automatically deleted on a First-In-First-Out (FIFO) basis.
Prior to version 3.5.1.22, historical event information would be automatically transferred to separate archive databases, but ONLY if the Archive Service had been configured. If the service had not been configured, some databases would become so large that it would impact the retrieval of report information and the time to complete full backups.
By default, Doors.NET will now store the last 2 million system transactions, the oldest events will then be deleted on a FIFO basis.
On a small system, 2 million transactions is likely to take months to reach, whereas on a very large system, this amount could be reached in a matter of a few days. Therefore, the value you set is dependent on how busy the system is and also how critical the historical event information is.
Configure the Maximum Number of Saved Events
- In Doors.NET, go to Setup then click on the System Options icon.
- The System Options Window will open.
- Click on Advanced Options.
- Locate the Database section.
- Set the maximum amount (in millions) that you wish to be kept in the database. The default value is 4 million.
Important Note: Use caution when setting this value (as an extremely large message table in the database can slow down the retrieval of certain report types). Rather than setting a maximum number of events to be stored you can also set the event storage for a maximum number of days. For example; keep only the last 90 days of system transactions.
- Make your selection and then save the settings.
Related Articles
Event Management and Event Settings
Effective from Doors.NET v_3.5.1.22, historical event information is automatically deleted on a First-In-First-Out (FIFO) basis. Prior to this version, historical event information would be automatically transferred to separate archive databases, but ...Event Monitoring
The Doors.NET software was designed to support both monitored and autonomous configurations. A system is considered to be monitored when there is an operator viewing events in real time - or responding to events as they happen. For example, a sound ...Live Events - Event Monitoring
Live Events Status displays real-time transactions as they occur and includes system messages with the newest transaction at the top of the window. Each column can be sorted or grouped to quickly find a specific item. If not already displayed, this ...Holidays - Special Event Types
The Holidays can be setup as 'Special Event' holiday types. These holidays do not affect other schedules. For example a Type 1 holiday set to being a special event will not have any effect on any other time schedules. The schedules will not be ...Event Display Colours
The Display Colors window allows you to set the colors of key event types that are displayed in the live events grid. It is helpful for operators who are color-blind and find it hard to distinguish between certain colors, i.e red and gray or yellow ...