During operation a lot of data is retained that is no longer needed. You need to delete this data on a regular basis to ensure an optimal performance.
Before deleting, you can export messages and events as backup in a CSV file. For more information refer to: CSV Export of Messages.
Deleting Completed Messages and Events on the Runtime Server
You can delete completed messages from the system. The total number of completed messages and events in the system should not exceed 100,000. Otherwise the performance may be affected.
- You are logged in as administrator on the runtime client.
- The Events/Messages perspective is displayed.
- The function has been performed in the quietest possible operating phase with few incoming messages.
- In the Message List view, click
Open View Menu.
- Select Remove all closed messages and related event.
- Click Yes.
- The 5,000 oldest completed messages and completed events are deleted from the database.
- If more than 5,000 messages exist, repeat the previous steps.
Deleting Completed Messages and Events Using Timers
You can set a timer for repeatedly deleting completed messages and events. The oldest message will be deleted first.
- The Administration perspective is displayed.
- Select System Engineering.
- Select Timer > Delete closed messages and events.
- In the Object Properties, you can edit the following attributes under Misc:
- Action: The Delete closed messages and events option is set by default.
- Action Parameters: You can enable the function by changing the string to disabled = false. You can also change the maximum number of entries in the Message List view by setting the entries_to_keep value to the required number, for example disabled=false&entries_to_keep =1000000.
- Cycle duration (ms): Define the time interval between two delete operations. By default, the time interval is set to 8,6400,000 ms, which means that the function will be performed once a day.
- Cycle iterations: To perform the action repeatedly, keep the default setting -1. To deactivate the timer, enter 0.
- Start Time: You can enter a start time for deleting completed messages and events.
Deleting Operator Log Entries
Operator logs are exported continually in accordance with the details in the configuration file /etc/viewpoint/logback.xml - via CSV export to the /var/log/viewpoint/log directory. The files are overwritten based on the MaxHistory, number of days or if the overall size totalSizeCap is exceeded. To delete data from the database, you can use a reminder timer.
- You are logged in as administrator on the runtime client.
- The Administration perspective is displayed.
- To define a timer for the runtime client, select System.
- Select Timer > Delete operator log entries.
- In the Object Properties, you can enter the following options under Misc:
- Action: The Cleanup Operator Logs option is set by default.
- Action Parameters: You can enable the function by changing the string to disabled = false. You can also change the maximum number of entries in the Operator Log by setting the entries_to_keep value to the required number, for example disabled=false&entries_to_keep =1000000.
- Start Time: You can enter a start time for deleting Operator log entries.
- Cycle iterations: To perform the action repeatedly, keep the default setting -1. To deactivate the timer, enter 0.
- Cycle duration: Define the time interval between two delete operations. By default, the time interval is set to 8,6400,000 ms, which means that the function will be performed once a day.
Deleting Cache Files on the Client
Data is buffered on various locations on the Windows client computer. In general, there is no need for action. However, if you want to install an update, this data should be deleted. Siveillance Control always creates temporary files.
- Open C:\Users\[Username]\.viewpoint.
- Before performing an update, delete the files in the directory.
- After successful update and login, a separate folder with a size of 120 to 150 MB will be created again per site.