Dyes Supported by the DyeInjection Monitor PROTOCOL Dye Flags

Configuring the DyeInjection Monitor to Manage Diagnostic Contexts 12-5 Example 12–1 Sample DyeInjection Monitor Configuration, in DIAG_MODULE.xml wldf-resource nameMyDiagnosticModulename instrumentation enabledtrueenabled wldf-instrumentation-monitor nameDyeInjectionname enabledtrueenabled dye-mask xsi:nil=truedye-mask propertiesADDR1=127.0.0.1 USER1=adminavitekproperties wldf-instrumentation-monitor -- Other elements to configure instrumentation -- instrumentation -- Other elements to configure this diagnostic monitor -- wldf-resource

12.3.1 Dyes Supported by the DyeInjection Monitor

The dyes available in the dye vector are listed and explained in the following table. Table 12–1 Request Protocols for Supported Diagnostic Context Dyes Dye Flags Description ADDR1 ADDR2 ADDR3 ADDR4 Use the ADDR1, ADDR2, ADDR3 and ADDR4 dyes to specify the IP addresses of clients that originate requests. These dye flags are set in the diagnostic context for a request if the request originated from an IP address specified by the respective property ADDR1, ADDR2, ADDR3, ADDR4 of the DyeInjection monitor. These dyes cannot be used to specify DNS names. CONNECTOR1 CONNECTOR2 CONNECTOR3 CONNECTOR4 Use the CONNECTOR1, CONNECTOR2, CONNECTOR3 and CONNECTOR4 dyes to identify characteristics of connector drivers. These dye flags are set by the connector drivers to identify request properties specific to their situations. You do not configure these directly in the Administration Console or in the descriptor files. The connector drivers can assign values to these dyes using the Connector API, so information about the connections can be carried in the diagnostic context. COOKIE1 COOKIE2 COOKIE3 COOKIE4 COOKIE1, COOKIE2, COOKIE3 and COOKIE4 are set in the diagnostic context for an HTTPS request, if the request contains the cookie named weblogic.diagnostics.dye and its value is equal to the value of the respective property COOKIE1, COOKIE2, COOKIE3, COOKIE4 of the DyeInjection monitor. DYE_0 DYE_1 DYE_2 DYE_3 DYE_4 DYE_5 DYE_6 DYE_7 DYE_0 to DYE_7 are available only for use by application developers. See Section 12.7, Using weblogic.diagnostics.context. 12-6 Configuring and Using the Diagnostics Framework for Oracle WebLogic Server

12.3.2 PROTOCOL Dye Flags

You must explicitly set the values for the dye flags USERn, ADDRn, COOKIEn, and CONNECTORn. in the DyeInjection monitor. However, the flags PROTOCOL_HTTP, PROTOCOL_IIOP, ROTOCOL_JRMP, PROTOCOL_RMI, PROTOCOL_SOAP, PROTOCOL_SSL, and PROTOCOL_T3 are set implicitly by WLDF. When the DyeInjection monitor is enabled, every request is injected with the appropriate protocol dye. For example, every request that arrives via HTTP is injected with the PROTOCOL_HTTP dye.

12.3.3 THROTTLE Dye Flag