Instrumentation Scope Configuration and Deployment Joinpoints, Pointcuts, and Diagnostic Locations
11.1.1 Instrumentation Scope
You can provide instrumentation services at the system level servers and clusters and at the application level. Many concepts, services, configuration options, and implementation features are the same for both. However, there are differences, and they are discussed throughout this documentation. The term server-scoped instrumentation refers to instrumentation configuration and features specific to WebLogic Server instances and clusters. Application-scoped instrumentation refers to configuration and features specific to applications deployed on WebLogic servers. The scope is built in to each diagnostic monitor; you cannot modify a monitors scope.11.1.2 Configuration and Deployment
Server-scoped instrumentation for a server or cluster is configured and deployed as part of a diagnostic module, an XML configuration file located in the DOMAIN_ NAMEconfigdiagnostics directory, and linked from config.xml. Application-scoped instrumentation is also configured and deployed as a diagnostics module, in this case an XML configuration file named weblogic-diagnostics.xml which is packaged with the application archive in the ARCHIVE_PATHMETA-INF directory for the deployed application.11.1.3 Joinpoints, Pointcuts, and Diagnostic Locations
Instrumentation code is inserted into or woven into server and application code at precise locations. The following terms are used to describe these locations: ■ A joinpoint is a specific location in a class, for example the entry andor exit point of a method or a call site within a method. ■ A pointcut is an expression that specifies a set of joinpoints, for example all methods related to scheduling, starting, and executing work items. The XML element used to describe a pointcut is pointcut. Pointcuts are described in Section 11.5.4.1, Defining Pointcuts for Custom Monitors. ■ A diagnostic location is the position relative to a joinpoint where the diagnostic activity will take place. Diagnostic locations are before, after, and around. The XML element used to describe a diagnostic location is location-type.11.1.4 Diagnostic Monitor Types
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