Configuring Data Retirement at the Server Level Configuring Age-Based Data Retirement Policies for Diagnostic Archives

6-4 Configuring and Using the Diagnostics Framework for Oracle WebLogic Server If you specify a JDBC resource but it is configured incorrectly, or if the required tables do not exist in the database, WLDF uses the default file-based persistent store.

6.4 Retiring Data from the Archives

WLDF includes a configuration-based data retirement feature for periodically deleting old diagnostic data from the archives. You can configure size-based data retirement at the server level and age-based retirement at the individual archive level, as described in the following sections.

6.4.1 Configuring Data Retirement at the Server Level

You can set the following data retirement options for a server instance: ■ The preferred maximum size of the server instances data store preferred-store-size-limit and the interval at which it is checked, on the hour, to see if it exceeds that size store-size-check-period. When the size of the store is found to exceed the preferred maximum, an appropriate number of the oldest records in the store are deleted to reduce the size below the specified threshold. This is called size-based data retirement. ■ Enable or disable data retirement for the server instance. For file-based diagnostic stores, this enables or disables the size-based data retirement options discussed above. For both file-based stores and database-based stores, this also enables or disables any age-based data retirement policies defined for individual archives in the store. See Section 6.4.2, Configuring Age-Based Data Retirement Policies for Diagnostic Archives, below.

6.4.2 Configuring Age-Based Data Retirement Policies for Diagnostic Archives

The data store for a server instance can contain the following types of diagnostic data archives whose records can be retired using the data retirement feature: ■ Harvested metrics data logical name: HarvestedDataArchive ■ Instrumentation events data logical name: EventsDataArchive ■ Custom data user-defined name Age-based policies apply to individual archives. The data store for a server instance can have one age-based policy for the HarvestedDataArchive, one for the EventsDataArchive, and one each for any custom archives. When records in an archive exceed the age limit specified for records in that archive, those records are deleted. Note: Size-based data retirement can be used only for file-based stores. These options are ignored for database-based stores. Note: WebLogic Server log files are maintained both at the server level and the domain level. Data is retired from the current log using the log rotation feature. See Configuring WebLogic Logging Services in Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server. Configuring Diagnostic Archives 6-5

6.4.3 Sample Configuration