WebLogic Log Requests Test

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: IP1:ALL,F0:192.168.10.7*,F3: 200*,COUNT(*),AVG(F4).

• Here, IP1 is just a display name that will be displayed in the eG monitor interface as a descriptor of this test.

• The term ALL instructs the eG Enterprise system to consider only those records that fulfill all the conditions that follow. Alternatively, the key word Any can be used, which implies that the eG Enterprise system, while monitoring, will consider even those records that fulfill either of the conditions that follow. The conditions are:

  • F0: 192.168.10.7* indicates that for a record to be considered for monitoring, the first field (i.e. the field with index 0) of the record should begin with the IP 192.168.10.1. Alternatively, the condition can be configured as F0:192.168.10.7*+192.168.10.8*+192.168.10.9*, where '+' denotes an 'OR' operator. This configuration indicates that for a record to be considered for monitoring, the first field of the record should begin with any of the three values configured - i.e. 192.168.10.7, 192.168.10.8, or 192.168.10.9.
  • F3: 200* indicates that for a record to be considered for monitoring, the fourth field (i.e. the field with index 3) of the record should begin with the number 200. Alternatively, the condition can be configured as F3:200*+300*+400*, where '+' denotes an 'OR' operator. This configuration indicates that for a record to be considered for monitoring, the fourth field of the record should begin with any of the three values configured - i.e. 200, 300, or 400.
• COUNT(*) returns the number of records that fulfill the configured criteria.
• AVG(F4) returns the average of the values of all the fields with index 4 (i.e. the fifth 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 starts with '192.168.10.1' and the fourth field starts with '200'. The number ‘200’ indicates a successful response. Therefore, this specification will report the metrics pertaining to only the successful responses for the IP patterns defined within the descriptor IP1 (i.e. 192.168.10.7*).

However, the test's configuration becomes complete only if the failure statistics are also extracted for IP1. Therefore, you will have to provide another search pattern for the descriptor IP1, so that the failure information is collected. The format of this pattern should be: IP1_FAIL: ALL,f0:192.168.10.7*,!f3:200*,COUNT(*),AVG(f4). Note that the descriptor names are the same, but the one meant for monitoring the failure cases, has been tagged as _FAIL. The specification !f3:200 indicates that the records with the number ‘200’ (in the fourth field) should NOT be considered for monitoring. ‘!’ is a NOT operator. Since ‘200’ represents a success state, !200 ensures that only the failed responses for IP1 are considered for monitoring.

The complete SearchPattern will hence be: IP1:ALL,f0:192.168.10.7*,f3:200*,COUNT(*),AVG(f4)#& IP1_FAIL:ALL,f0:192.168.10.7*,!f3:200*,COUNT(*),AVG(f4), where #& is the separator.

In the monitor interface however, the descriptor IP1 alone will appear, but when clicked, will display both the success and failure statistics for the pattern 192.168.10.7*. Therefore, it is imperative that the WLLogReqTest be configured in such a way that it tracks both the success and failure cases for every IP pattern configured for monitoring. Otherwise, the test will not function as desired. This implies that if an IP pattern IP2 is configured for monitoring successful responses, then an IP2_FAIL should follow to monitor the failed responses. Similarly, multiple patterns can be configured for monitoring, separated by ‘#&’.