Comparing System-Scoped to Application-Scoped Instrumentation
11.5.1 Comparing System-Scoped to Application-Scoped Instrumentation
Instrumenting an application is similar to instrumenting at the system level, but with the following differences: ■ Applications can use standard, delegating, and custom monitors. – The only server-scoped standard monitor is DyeInjection. The only application-scoped standard monitor is HttpSessionDebug. For more information, see the entry for HttpSessionDebug in Section B.1, Diagnostic Monitor Library. – Delegating monitors are either server-scoped or application-scoped. Applications must use the application-scoped delegating monitors. – All custom monitors are application-scoped. ■ The servers instrumentation settings affect the application. In order to enable instrumentation for an application, instrumentation must be enabled for the server on which the application is deployed. If server instrumentation is enabled at the time of deployment, instrumentation will be available for the application. If instrumentation is not enabled on the server at the time of deployment, enabling instrumentation in an application will have no effect. ■ Application instrumentation is configured with a weblogic-diagnostics.xml descriptor file. You create a META-INFweblogic-diagnostics.xml file, configure the instrumentation, and put the file in the applications archive. When the archive is deployed, the instrumentation is automatically inserted when the application is loaded. ■ You can use a deployment plan to dynamically update configuration elements without redeploying the application. See Section 14.2, Using Deployment Plans to Dynamically Control Instrumentation Configuration. The XML descriptors for application-scoped instrumentation are defined in the same way as for server-scoped instrumentation. You can configure instrumentation for an application solely by using the delegating monitors and diagnostic actions available in the WLDF Instrumentation Library. You can also create your own custom monitors; however, the diagnostic actions that you attach to these monitors must be taken from the WLDF Instrumentation Library. Table 11–5 compares the function and scope of system and application diagnostic modules. Table 11–5 Comparing System and Application Modules Module Type Add or Remove Objects Dynamically Add or Remove Objects with Console Modify with JMX Remotely Modify with JSR-88 non-remote Modify with Console EnableDisable Dye Filtering and Dye Mask Dynamically System Module Yes Yes Yes No Yes via JMX Yes Application Module Yes, when hot-swap is enabled No, when hot-swap is not enabled: module must be redeployed Yes No Yes Yes via plan Yes Configuring Instrumentation 11-1311.5.2 Overview of the Steps Required to Instrument an Application
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