WebLogic Log Patterns Test

This test monitors an application log and reports measures such as the total number of responses that have been logged and average response time of every log file entry pattern that has been configured.

Target of the test : A WebLogic server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every server being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


The host for which the test is to be configured.


The port at which the application listens.


Specify the full path to the log file to be monitored.


The records in the log file that need to be considered for monitoring will have to be provided in the RecordPattern text box. The pattern configuration should be in the following format: {f0}sep1{f1}sep2{f2}, where {f0}, {f1}, and {f2} represent the indexes of the first, second, and third fields (respectively) of the records logged in the log file, and sep1 and sep2 are the separators after {f0} and {f1} respectively. A separator can be a combination of any number of characters.

For example, take the case of a log file with the following entry:

eg_sample_appln_jsp :;TIME:2005-01-01 00:06:26.904;Thread_ID:ExecuteThread: '48' for queue: default';Duration:233

To ensure that the above record is considered for monitoring, the record pattern will have to be specified as follows: {f0};{f1};{f2};{f3}:{f4}, where {f0} represents the first field of the record, which is followed by the separator ';', and so on.


Of the records that match the configured RecordPattern, the eG agent will search for and monitor only those records which match the string patterns specified in the SearchPattern text box. To help you understand how to configure a SearchPattern, let us take the example of the following search pattern: Info1:any,f0:*eg_sample_appln_jsp *,count(*),avg(f4).

  • Here, Info1 is just a display name that will be displayed in the eG monitor interface as a descriptor of this test.
  • Use the term ALL or Any to instruct the eG Enterprise system to consider only those records that fulfill the condition that follows, for monitoring. The condition is: f0:*eg_sample_appln_jsp*. This indicates that for a record to be considered for monitoring, the first field (i.e. the field with index 0) of the record should embed the string eg_sample_appln_jsp.
  • COUNT(*) returns the number of records that fulfill the configured criteria.
  • AVG(f5) returns the average of the values of all the fields with index 5 (i.e. the sixth field), in the records that match the configured criteria.

According to this specification, the eG Enterprise system, while taking a count and while calculating the average, will consider only those records where the first field embeds the string eg_sample_appln_jsp. Similarly, multiple search patterns can be provided separated by "#&".

Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates the number of account calls that are being made during a period of time.


A high value of this measure indicates a heavy workload on the server.

Avg response time

Indicates the average response time for account calls.


A dramatic increase in this value may be indicative of poor responsiveness of the server.


If any of the measures of this test returns the value -5, then such a measure will not be displayed in the monitor interface. On the other hand, if all the measures of this test return the value -5, then all the measures will appear in the monitor interface, but the value displayed for each measure will be "Not Available".