Storage Reduction and Performance Stabilization

Storage Reduction

Monitoring Console stores all monitor execution results and all result files, like TrueLog files, .wrt files, and others, in the repository. If you run multiple monitors over a long period of time, you may want to save space on the hard drive of your database server. This feature is only supported by Monitoring Console. Monitoring Console offers the following two options for storage reduction:
Reducing storage by removing old result files (TrueLog files, .wrt files, etc.) from the repository
Result files are stored as BLOBs in the repository. You might, for example, set up storage reduction so that when result files in the repository reach a size of 20 GB (GigaBytes), the oldest result files are removed as new result files are written to the repository.
Reducing storage by aggregating monitoring results
While Monitoring Console saves raw monitoring values by default, you may not need such a level of detail for older results. You can advise Monitoring Console to aggregate results after defined time intervals into units of 15 minutes, 1 hour, 1 day, or 1 week. You might for example, with data older than 1 month, reduce the detail level of results to an aggregated value of 15 minutes intervals. For data older than 6 months, you could reduce the detail level of results to an aggregated value of 1 hour intervals. For data older than 1 year, you might reduce the detail level of results to an aggregated value of 1 day intervals. For data older than 2 years, you could reduce the detail level of results to an aggregated value of 1 week intervals.

Performance Stabilization

By default, the history of the project health is not being re-calculated after deleting a monitor. This guarantees that database performance is consistent. However, if you want to have the historical project health data be re-calculated to reflect the missing monitor, you can turn this on in the SvAppServerHomeConf.xml file. Be aware that if you turn this on, the database takes a severe performance hit every time a monitor is being deleted.