The DIAG_MODULE.xml Resource Descriptor Configuration Managing Diagnostic System Modules
4.6.3 The DIAG_MODULE.xml Resource Descriptor Configuration
Except for the name and list of targets, which are listed in the config.xml file, as described above, all configuration for a diagnostic system module is saved in its resource descriptor file. Example 4–3 shows portions of the descriptor file for a diagnostic system module named myDiagnosticModule. Example 4–3 Sample Structure of a Diagnostic System Module Descriptor File, MyDiagnosticModule.xml wldf-resource xmlns=http:xmlns.oracle.comweblogicweblogic-diagnostics xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:xmlns.oracle.comweblogicweblogic-diagnostics1.0webl ogic-diagnostics.xsd nameMyDiagnosticModulename instrumentation -- Configuration elements for zero or more diagnostic monitors -- instrumentation harvester -- Configuration elements for harvesting metrics from zero or more MBean types, instances, and attributes -- harvester watch-notification -- Configuration elements for one or more watches and one or more notifications-- Understanding WLDF Configuration 4-7 watch-notification wldf-resource4.6.4 Managing Diagnostic System Modules
A diagnostic system module can be targeted to zero, one, or more servers or clusters, although a given server can have only one module targeted to it at a time. You can create multiple modules that monitor different aspects of your system. You can then choose which module to target to a server or cluster, based on what you want to monitor at that time. Because you can target the same module to multiple servers or clusters, you can write general purpose modules that you want to use across a domain. You can change the target of a diagnostic module without restarting the server instances to which it is targeted or untargeted. This gives you considerable flexibility in writing and using diagnostic monitors that address a specific diagnostic goal, without interfering with the operation of the server instances themselves.4.6.5 More Information About Configuring Diagnostic System Resources
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