...
There are a few different ways to trim out historical performance data from your DataStore. The most simplistic method is to change your up.time Uptime Infrastructure Monitor archive policy to the number of months that you would like to maintain but you can also run manual SQL commands to remove very specific sets of data. For trimming specific performance data please refer to the following articles: Manually trim performance data from a MySQL DataStore, Manually trim performance data from a MS SQL DataStore, or Manually trim performance data from an Oracle DataStore.
...
- Change the archive policy to the number of months that you want to retain -- for example one month. To reduce the amount of data that up.time Uptime Infrastructure Monitor keeps in the DataStore, make the the number of months smaller than the current number.
- Stop and then restart the up.time Uptime Infrastructure Monitor Data Collector using the following commands: Starting (or restarting) and Stopping Uptime Infrastructure Monitor
When up.time Uptime Infrastructure Monitor restarts, it should start archiving data. The archived files will be placed in the directory <uptime_dir>/archives. Once the archiving process is completed, the entry Finished Archiving should appear in the file <uptime_dir>/logs/uptime.log.
...
To export your configuration and performance information, first stop the uptime_core or Data Collector service, so that up.time Uptime Infrastructure Monitor isn't actively writing to the database: Starting (or restarting) and Stopping Uptime Infrastructure Monitor
...
The command above dumps your up.time Uptime Infrastructure Monitor DataStore information into a simple text file named export.txt. This file will be very large, so plan for this command to take some time to complete. The settings used below are based on a default up.time Uptime Infrastructure Monitor installation. Check your uptime.conf file for the settings that are specific to your installation.
...
To rebuild your DataStore, perform the following steps. This process will remove all up.time Uptime Infrastructure Monitor data from the DataStore. Be sure that you have completed step 2 above to backup your configuration before performing these steps.
- Run the following commands to delete the up.time Uptime Infrastructure Monitor DataStore:
On Linux systems:
Code Block > mysql -uuptime -puptime -P3308 --protocol=tcp mysql> use uptime; mysql> drop database uptime; mysql> exit; > /etc/init.d/uptime_datastore stop
On Windows systems:
Code Block > mysql -uuptime -puptime -P3308 --protocol=tcp mysql> use uptime; mysql> drop database uptime; mysql> exit; > net stop "up.time Data Store"
Delete the following files from your DataStore directory:
No Format ibdata1 ib_logfile0 ib_logfile1
- Run the following commands to restart your database and rebuild your DataStore:
On Linux systems:
Code Block > /etc/init.d/uptime_datastore start > mysql -uuptime -puptime -P3308 --protocol=tcp mysql> create database uptime; mysql> exit; > mysql -uuptime -puptime -P3308 --protocol=tcp -A -N -f uptime < export.txt
On Windows systems:
Code Block > net start "up.time Data Store" > mysql -uuptime -puptime -P3308 --protocol=tcp mysql> create database uptime; mysql> exit; > mysql -uuptime -puptime -P3308 --protocol=tcp -A -N -f uptime < export.txt
Run the following commands to restart the remaining up.time Uptime Infrastructure Monitor processes:
On Linux systems:
Code Block language text /etc/init.d/uptime_core start /etc/init.d/uptime_httpd start /etc/init.d/uptime_controller start
On Windows systems:
Code Block language text > net start "up.time Data Collector" > net start "up.time Web Server" > net start "up.time Controller"