Configuring Data Retirement at the Server Level Configuring Age-Based Data Retirement Policies for Diagnostic Archives
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-56.4.3 Sample Configuration
Parts
» Oracle Fusion Middleware Online Documentation Library
» What Is the WebLogic Diagnostics Framework?
» Document Scope and Audience Guide to This Document
» Data Creation, Collection, and Instrumentation Archive
» Monitoring Dashboard Diagnostics Request Performance Page
» Watch and Notification Data Accessor Diagnostic Image Capture
» How It All Fits Together About Oracle JRockit Flight Recorder
» Key Features of WLDF Integration with JRockit Flight Recorder
» JFR Graphical User Interface
» Displaying Event Data for a Product Subcomponent Viewing the Event Log to Display Details
» Tracking Execution Flow by Analyzing an Operative Set
» Changing the Location of Temporary JFR Files
» Obtaining the JRockit Flight Recording File Configuration MBeans and XML
» Tools for Configuring WLDF Configuring Diagnostic Image Capture and Diagnostic Archives
» The DIAG_MODULE.xml Resource Descriptor Configuration Managing Diagnostic System Modules
» WLDF Configuration MBeans and Their Mappings to XML Elements
» Configuring WLDF Diagnostic Volume WLST Commands for Generating an Image Capture
» Creating WLDF Tables in the Database
» Harvesting, Harvestable Data, and Harvested Data
» Configuring the Harvester Sampling Period Configuring the Types of Data to Harvest
» Sample Configurations for Different Harvestable Types
» Harvesting Data from the Different Harvestable Entities Watches and Notifications
» Sample Watch and Notification Configuration
» Types of Watches Configuration Options Shared by All Types of Watches
» Configuring Harvester Watches Oracle Fusion Middleware Online Documentation Library
» Configuring Log Watches Configuring Instrumentation Watches
» Defining Watch Rule Expressions Types of Notifications
» Configuring JMX Notifications Configuring JMS Notifications
» Configuring SNMP Notifications Oracle Fusion Middleware Online Documentation Library
» Configuring SMTP Notifications Configuring Image Notifications
» Instrumentation Scope Configuration and Deployment Joinpoints, Pointcuts, and Diagnostic Locations
» Diagnostic Monitor Types Concepts and Terminology
» Instrumentation Configuration Files Oracle Fusion Middleware Online Documentation Library
» Instrumentation XML Elements XML Elements Used for Instrumentation
» wldf-instrumentation-monitor XML Elements XML Elements Used for Instrumentation
» Configuring Server-Scoped Instrumentation Oracle Fusion Middleware Online Documentation Library
» Comparing System-Scoped to Application-Scoped Instrumentation
» Defining Pointcuts for Custom Monitors
» Creating Request Performance Data
» Context Life Cycle and the Context ID Dyes, Dye Flags, and Dye Vectors
» Dyes Supported by the DyeInjection Monitor PROTOCOL Dye Flags
» THROTTLE Dye Flag When Diagnostic Contexts Are Created
» Configuring Delegating Monitors to Use Dye Filtering
» Dye Filtering Example How Dye Masks Filter Requests to Pass to Monitors
» Configuring the THROTTLE Dye
» How Throttling is Handled by Delegating and Custom Monitors
» Using weblogic.diagnostics.context
» Data Stores Accessed by the Data Accessor Accessing Diagnostic Data Offline
» Accessing Diagnostic Data Programmatically
» Using Deployment Plans to Dynamically Control Instrumentation Configuration
» Using a Deployment Plan: Overview Creating a Deployment Plan Using weblogic.PlanGenerator
» Sample Deployment Plan for Diagnostics
» View List About the Monitoring Dashboard Interface
» Metric Browser About the Monitoring Dashboard Interface
» Current Time Range Charts Custom Time Range Charts
» Sequence in which Metrics Data is Displayed
» Notes about Metric Data Retention
» How WLDF Generates and Retrieves Data Mapping WLDF Components to Beans and Packages
» Configuration APIs Configuration and Runtime APIs
» Runtime APIs Configuration and Runtime APIs
Show more