String Search

The String search tool enables you to fine-tune your monitoring on all the application classes of the BMC Performance Manager Express Monitoring Studio package.

What you can do with this tool

Monitoring Studio Express offers a powerful string search capability. You can search for strings that must "be found" or "not be found" in a given source.

•	A "must be found" string search looks through the specified source and triggers an alert if the specified string is not found.

•	A "must not be found" string search triggers an alert when the specified string is found.

You can set up string searches on the instances of all the application classes of BMC Performance Manager Express Monitoring Studio: Command Line Analysis, Database Query Analysis, Java MBean Polling (JMX) Polling, LOG File Monitoring and Analysis, SNMP Polling, WMI Query Analysis and Web Request Analysis. You can set alert thresholds for the string searches, and make your monitoring more proactive and powerful.

Editing or Deleting an instance

The basic mechanism is:

1.	Specify an information source

2.	Specify what the source must contain or must not contain (a combination of two regular expressions)

3.	Indicate the string’s location i.e. where to look for this string (anywhere in the line, column number, and which lines: all lines, or specific lines)

4.	Monitoring Studio Express will report the number of lines that match the specified criteria

The string search tool is integrated within each of the monitoring tools/application classes, so this enables you to add the string search during creation itself of an application class instance, or at any time later after creation of the instance. An instance can have several string searches running on it. Alert thresholds can be set for all the string search instances.

The string search runs differently on running sources such as LOG files – where it searches only amongst the new lines appended since the last poll; whereas for flat sources, the entire information source is searched (as per the indications specified: what; where etc).

For string searches on LOG files, please see the corresponding topic: String Search on LOG files.

Parameters

•	Count (LB)

•	Count (HB)

•	Matching Lines

(HB) = "Higher is Better" and (LB) = "Lower is Better". HB and LB parameters will always display the same value since, basically, both represent the same value. The purpose of having two parameters for the same value is to be able to set different alert thresholds depending on the nature of the monitored object. For instance, an alert can be set to be triggered on the HB parameter when the value dips too low (it breaches the lower threshold of the range) and an alert can be set on the LB parameter to go off when the value rises too high. The setting of alerts is flexible and can be done on either of the two parameters, on both, or on neither; it depends entirely on nature of the monitored object and the user's specific needs.

Details of the parameters and alert conditions are stated in the Reference Guide.