| |
Note: As of WebLogic Server 12.2.1, the WLDF query language is deprecated and is replaced by the Java Expression Language (EL). However, the Administration Console still supports existing policy expressions constructed in the WLDF query language.
A policy expression may include the following:
You can create policies based on log events, on harvested attributes, and on attributes of records from instrumentation events (triggered by diagnostic monitors). The variables you use to create the expression are different, depending on the type of policy. The variables available for each of these types are explained in the following tables.
A log event policy expression refers to attributes of a log message from the server log or domain log. The following table shows the variable names for those attributes:
| Variable | Description | Data Type |
|---|---|---|
| ID | ID of the log message (usually starts with "BEA="). | String |
| MACHINENAME | Name of machine that generated the log message. | String |
| SERVERNAME | Name of server that generated the log message. | String |
| THREADNAME | Name of thread that generated the log message. | String |
| USERID | ID of the user that generated the log message. | String |
| TRANSACTIONID | JTA transaction ID of thread that generated the log message. | String |
| SEVERITY | I18N severity text of log message. These values are OFF, EMERGENCY, ALERT, CRITICAL, NOTICE, ERROR, WARNING, INFO, DEBUG, and TRACE. | String |
| SUBSYSTEM | Name of subsystem emitting the log message. | String |
| TIMESTAMP | Timestamp when the log message was created. | Long |
| LOGMESSAGE | Message content of the log message. | String |
| THROWABLE | Exception associated with this log event. This is created
by calling the toString method of the
exception. |
String |
An example log event policy expression is:
(Severity = 'Warning') AND (Id = 'BEA-320012')
An instrumentation event data policy expression refers to attributes of a data record from the instrumentation event. The following table shows the variable names for those attributes:
| Variable | Description | Data Type |
|---|---|---|
| TIMESTAMP | Timestamp when the instrumentation event was created. | Long |
| CONTEXTID | Diagnostic context ID of instrumentation event. | String |
| TRANSACTIONID | JTA transaction ID of thread that created the instrumentation event. | String |
| USERID | ID of the user that created the instrumentation event. | String |
| ACTIONTYPE | Type of instrumentation action. | String |
| DOMAINNAME | Name of domain. | String |
| SEVERNAME | Name of server that created the instrumentation event. | String |
| SCOPENAME | Name of instrumentation scope. | String |
| MONITORTYPE | Type of monitor. | String |
| SOURCEFILE | Source file name. | String |
| LINENUMBER | Line number in source file. | Integer |
| CLASSNAME | Class name of joinpoint. | String |
| METHODNAME | Method name of joinpoint. | String |
| METHODDESCRIPTOR | Method arguments of joinpoint. | String |
| RETURNVALUE | Return value of joinpoint. | String |
| PAYLOAD | Payload of instrumentation event. | String |
An example instrumentation event data policy expression is:
(ActionType = 'ThreadDumpAction')
A harvesterpolicy expression refers to attributes that are being harvested. The expression must include an ObjectName or ObjectName pattern. For more information, see "Configuring the Types of Data to Harvest".
The following example shows an expression that includes the complete MBean ObjectName.
${mydomain:Name=HarvesterRuntime,Location=myserver,Type=HarvesterRuntime,ServerRuntime=myserver,Attribute=TotalSamplingCycles} > 10
 |