On the first day of each month, the archive process will remove all performance metrics from the up.time DataStore that are older than the specified number of months in the Archive Policy.
For example, if Overall CPU / Memory Statistics is set to 6 months, on the first of the month when the archiving process runs, all CPU and memory metrics older than six months will be removed from the up.time DataStore. If archived data is required for graphing or reporting purposes, it can be imported back into up.time by using the restorearchive tool, which can be found in the uptime scripts directory. Note: archiving large sets of performance data may time out. If this occurs, contact [email protected] to discuss alternate methods for removing un-needed historical performance metrics. |
How do I change my archiving policy? | Rating | Views | |
---|---|---|---|
To set an archive policy, do the following: 1. On the up.time tool bar, click Config. 2. In the Tree panel, click Archive Policy. 3. Specify the number of months worth of data that you want to... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-26-2011 | Index: 328 |
3618 |
How does the SQL Server Tablespace Check monitor work? | Rating | Views | |
---|---|---|---|
The SQL Server Tablespace Check monitor works by connecting directly to your database instance and running a set of commands to verify tablespace usage. The commands used are sp_helpdb; From this... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 296 |
4947 |
Does the HTTP monitor work with NTLM authentication? | Rating | Views | |
---|---|---|---|
Current Windows based NTLM authentication to web sites is not supported by the HTTP or Web Application Transaction service monitors. By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-10-2011 | Index: 304 |
3192 |