oracle IM Configuration

This article describes the configuration concepts and procedures to set up the Oracle Database Monitoring (oracle) probe. To configure the probe, you must create a connection to the Oracle database and a monitoring profile. The default checkpoints are automatically added to a new profile. Profile checkpoints are predefined parameters that can be used to monitor the server performance or unwanted events. You can generate alarms and QoS using these checkpoints. Each monitoring profile runs in its own thread, which keeps the monitoring profile in isolation
uimpga-ga
oracle_IM
This article describes the configuration concepts and procedures to set up the Oracle Database Monitoring (oracle) probe. To configure the probe, you must create a connection to the Oracle database and a monitoring profile. The default checkpoints are automatically added to a new profile. Profile checkpoints are predefined parameters that can be used to monitor the server performance or unwanted events. You can generate alarms and QoS using these checkpoints. Each monitoring profile runs in its own thread, which keeps the monitoring profile in isolation
The Oracle client or server is mandatory for the oracle probe to work.
This article is for probe versions 5.0 and later.
The following diagram outlines the process to configure the probe.
Configure oracle on IM
Configure oracle on IM
Contents
2
Verify Prerequisites
Review the following prerequisites before you configure the probe:
(Optional) Configure General Properties
You can change the default configuration of your probe if these settings do not meet your requirements. After the probe installation, it is active and immediately attempts to publish data. You can configure the following general properties of the probe:
  • Alarm parameters
  • Logging properties
Follow these steps:
  1. Navigate to the
    Setup > General
    tab.
  2. Set or modify the following information, as required:
    • Generate status only:
      specifies the probe to only generate status and not to issue an alarm when a threshold is breached.
      Default: Not selected
    • Clear alarms on restart
      : clears all alarms when the probe is restarted.
      Default: Selected
    • Alarm severity filter
      : specifies a severity level filter on events to be considered as alarms. Events matching the selected severity level and higher, generate alarms. If major is selected, then only the messages with severity level as major and above are considered as alarms.
      Default: information
    • Status Auto-Update:
      allows you to automatically refresh the Status tab based on the defined number of seconds.
      Default: Not selected
      The Auto-Update value is saved in the configuration file but the check box is cleared when you restart the probe.
    • Log Size
      : specifies the maximum size of the probe log file in kilobytes. When this size is reached, the existing contents of the file are cleared.
      Default: 100 KB
    • Log Level
      : specifies the level of information that is written in the log file.
      Default: Less Detail
      Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging.
Create a Connection
You can create a connection to the Oracle database that you want to monitor. Specify the user ID, password, and service name you want to use to connect to the database.
To monitor a CDB and PDB in Oracle 12c databases, you must create separate connections for each database type.
Follow these steps:
  1. Right-click in the
    Connections
    tab and select the
    New
    option.
    The
    Add New Connection
    dialog displays.
  2. Enter a connection
    Name
    and click
    OK
    .
    The
    New Connection
    dialog displays.
  3. Specify the following information:
    • Description:
      specifies additional information about the connection.
    • User ID:
      defines the user ID with authorization to read the database views.
    • Password:
      specifies the password for the defined
      User ID
      . The password is encrypted and placed into the configuration file.
    • Service Name:
      specifies the service name that is defined in the
      tnsnames.ora
      file.
    • Retry attempts:
      specifies the number of attempts that the probe makes to connect when there is a failure. The value 0 means only the initial connection is attempted.
      Default: 0
    • Retry delay:
      specifies the time the probe waits between two connection attempts.
      Default: 1 sec
    • Skip Privilege Check:
      allows you to create custom checkpoints for users who do not have DBA and the Select Catalog Role privileges on the database. It is assumed that you would provide valid instance information and database version. Selecting this field may affect the execution of normal checkpoints which require Select Catalog Role privileges.
      Default: Not selected
      When you select the
      Skip Privilege Check
      field enables:
      • The
        DB Version
        and
        Instance
        fields.
      • The execution of normal checkpoints that require Select Catalog Role privileges.
    • DB Version:
      defines the version of the database that is used for the connection. For example, mention 12 for an Oracle 12 database.
    • Instance:
      specifies the instance name to establish the connection.
  4. Click
    Test
    .
    The connection to the database server is verified when the icon turns green.
  5. Click
    OK
    .
The new connection is added to the
Connections
dialog.
  • To copy a connection, right-click the connection and select
    Copy
    .
  • To edit a connection, right-click the connection and select
    Edit
    .
  • To delete a connection, right-click the connection and select
    Delete
    .
  • To rename a connection, right-click the connection and select
    Rename
    . When you rename a connection, the Unified Management Portal (UMP) displays two nodes for the same connection. For more information, see Rename Connection or Profile.
  • When you edit a connection for monitoring a CDB or a PDB Oracle instance; test the connection after editing to ensure a successful connection. This test is required as the PDB_Count checkpoint needs connection information before it generates any user-defined alarms or QoS.
Create a Group
You can create a group to categorize the profiles in the probe. You can use groups to manage large configurations monitoring.
Follow these steps:
  1. Navigate to the
    Groups
    tab.
  2. Right-click in the tab and select
    New
    .
  3. Specify a
    Name
    for the group.
  4. Click
    OK
    .
Create a Profile
You can create profiles to monitor Oracle databases using the connections in the probe. Every profile runs as a separate thread, and multiple profiles can be used to monitor one instance. You can configure the probe to deploy available resources the best way and allow independent monitoring of several instances simultaneously. To monitor a CDB and a PDB in Oracle 12c database, create separate profiles for each database type. A CDB profile does not monitor the PDBs linked to the CDB.
The following icons denote the profile status:
  • Green-icon.png indicates that the profile is active and running.
  • Yellow icon.png indicates that the profile is active but not being monitored.
  • Black-icon.png indicates that the profile is inactive.
Follow these steps:
  1. Right-click in the
    Profiles
    tab and select the
    New
    option.
    The
    Add New Profile
    dialog appears.
  2. Enter the profile name and click
    OK
    .
    The
    New Profile
    dialog appears. The upper part of the window shows general profile properties and defaults. The lower part of the window displays a list of available profile checkpoints.
  3. Specify the following information:
    • Active:
      activates the profile for monitoring on creation.
      Default: Selected
    • Description
      : specifies additional information about the profile.
    • Heartbeat
      : specifies the interval after which schedules of all profile checkpoints are tested and executed.
      Default: 5 sec
      This number is a common denominator to all check interval values. The higher the value, the lower is the profile overhead.
    • Connection
      : specifies the connection that is used in the profile. The connections must exist in the probe before creating a profile.
    • Check Interval
      : specifies the interval after which the profiles are scanned. The activated checkpoints use this interval if no
      Check Interval
      is defined for them.
      Default: 5 min
      • Reduce this interval to generate alarms and QoS frequently. A shorter interval can also increase the system load.
      • If you change this interval after activating the checkpoints, the checkpoints continue to generate alarms and QoS on the previous interval.
    • Clear message:
      specifies the message that is generated for the timeout clear alarm.
      Default: timeout_clear_1
    • SQL Timeout:
      specifies the SQL query timeout. Every checkpoint query runs asynchronously. If the query reaches the SQL timeout, the checkpoint processing is terminated. The probe processes the next checkpoint and generates an alarm.
      Default: 30 sec
      On every check interval, the SQL timeout alert is first cleared on the basis of query for a particular checkpoint. The SQL timeout alert is thrown again if the issue remains.
    • Message:
      specifies the message for the SQL query timeout alarm.
      Default: sql_timeout_1
    • Profile Timeout:
      defines the maximum processing time for all checkpoints in the profile. If this timeout is reached, the interval processing is terminated. The probe waits for next heartbeat to evaluate any checkpoint schedules, and generates an alarm.
      Default: 15 min
    • Message:
      specifies the message for the profile timeout alarm.
      Default: p_timeout_1
    • Timeout severity:
      specifies the severity for timeout messages.
      Default: major
    • Group:
      allows you to select the defined groups from the
      Groups
      tab. This value is blank, by default.
    • Alarm source:
      overrides the source name of the alarm on the Unified Service Management (USM). If you do not specify a value, robot IP address is used.
    • Connection failure message:
      specifies the message that is displayed when the probe is unable to connect to the Oracle database.
      Default: connect_failed_1
    • (For Version 5.0 and later) Use Alarm Source As QoS Source:
       specifies the probe to use the
      Alarm source
      value as the QoS Source.
      Default: Not selected
      CA does not recommend you to change the source fields after the initial configuration. If you change the QoS source later, multiple graphs are displayed on the USM Metrics view (one for every QoS source value). Also, CA recommends you to keep the source identical for both alarm and QoS.
  4. Select the required checkpoints in the
    Profile Checkpoints
    section.
    You can also configure the checkpoints, as required.
  5. Click
    OK
    .
CA does not recommend you to delete the default threshold of the following checkpoints, as the probe cannot generate alarms or QoS:
  • locked_users
  • long_queries
  • no_next_extents
  • tablespace_deficit
  • user_locks
For example, if a checkpoint has a count threshold, the threshold and alarm will not work unless the default threshold is breached and an alarm is generated.
  • The checkpoints are added to your profile and use the global and default checkpoint settings, unless you modify the settings locally for your profile. If you want specific settings for only one profile, right-click the checkpoint in the list and select
    Change to Static
    . Such checkpoints apply to the selected profile.
  • To modify a profile, right-click on it and select
    Edit
    .
  • To delete a profile, right-click on it and select
    Delete
    .
  • To rename a profile, right-click the profile and select
    Rename
    . When you rename a profile, the UMP displays two nodes for the same profile. For more information, see Rename Connection or Profile.
  • To copy the attributes of a profile to another, right-click on it and select
    Copy
    .
  • To stop the profile from monitoring, right-click on it and select
    Suspend
    .
  • To resume monitoring of a suspended profile, right-click on it and select
    Resume
    .
(Optional) Create Custom Checkpoints
You can create a checkpoint and configure its properties to monitor the server performance or unwanted events. When the configured profile runs on the server, the set criteria for the checkpoints are scanned against the real-time objects. If any unwanted event occurs, the probe generates alarms or QoS messages. When you change the template value, it reflects on all profiles using dynamic templates strategy.
Follow these steps:
  1. Navigate to the
    Templates
    tab.
  2. Right-click in the checkpoints list and select
    Create new
    .
  3. Enter a checkpoint name and click
    OK
    .
    The
    Edit template checkpoint [
    checkpoint name
    ]
    appears.
  4. Navigate to the
    Query
    tab.
  5. Click the
    Edit/New
    button and define the connection details. For more information, see Create a Connection.
    • The connection information defined in this form must be same as defined in the oracle profile.
    • If there are multiple profiles using different connections, then the custom checkpoints must be converted to static and in each static checkpoint, the connection should match with the connection used in the oracle profile.
  6. Enter the required query statement in the
    Query
    text box and click
    Test
    to validate the query.
    The
    Query Result
    dialog appears, displaying the query result. A single query is executed for all Oracle databases. If any database is unable to execute the query, the probe generates a failure message. The query has to return at least one numeric column that will be used as Checked value (all numeric formats are supported). If the query returns more than one row, the probe needs unique identification per row. This will be used as part of suppression key and QoS definition. The row key can be created by concatenating several columns in the checkpoint definition. Additional columns can be retrieved to be used in generated messages.
    Use rtrim and ltrim functions to remove leading and trailing blanks from string variables. Use explicit column names for manipulated values. Avoid generated names, such as Col0 and Col1.
    If query takes more than 30 seconds to fetch the data then probe will give the error as “profile timeout [30sec] reached” in probe logs.
    Follow the below steps to increase the timeout more than 30 sec:
    1. Open the Oracle probe in Raw Configure.
    2. Add the follow as a Key and Value under "setup". test_profile_timeout = 10 min (or any value based on requirement can be in sec/min/hr).
  7. Click
    Close
    .
  8. Set or modify the following information, as required:
    • Row identification
      : specifies the unique identification code of the row for which reporting is done.
    • Message variables
      : specifies the variables to be used in the message. Click
      Edit
      to select the variables to be used in the message. A new dialog opens with a list of all available columns, their data type and possible usage. Specify the
      Column use
      for the following data types as specified:
      Numeric
      data type:
      • Value
        : specifies the value for verifying the checkpoint.
      • Value size
        : specifies the file size (in B, KB, MB, GB or TB).
      • Value int
        : specifies the integer number.
      • Information
        : specifies the standard formatting (if available 2 digits after comma).
      Character
      data type:
      • Row key
        : specifies the row identification for string formatting.
      • Information
        : specifies the string formatting.
    • Query file
      : specifies the file that stores the query. Each query is stored in separate files. Click the
      Read
      button to read the SQL query stored in the file. The query file name should contain full path, otherwise the file will be stored in the probe work directory.
    • Interval modus
      : enables you to subtract the variable value from the value generated at the end of the interval. On selecting the
      Interval modus
      check box, the variable $column_interval_value.i is added to the
      Message variables
      text box. This list can be viewed in the
      Edit Threshold
      dialog box. The
      interval_value
      variable can be configured from the probe
      Raw Configuration
      interface. If you do not select the
      Interval modus
      check box, the value of variable as returned from the query will be used for checking and QoS.
  9. Navigate to the
    General
    tab and specify the following information, as required:
    • Description:
      provides additional information about the checkpoint.
    • Active:
      activates the checkpoint for monitoring, on selection.
    • Send Quality of Service:
      specifies the probe to send QoS data into the database. If it is not available for a checkpoint, this field is disabled.
    • QoS List:
      allows you to define QoS to be used in the checkpoint. Click the
      QoS List
      ( single_arrow.png ) icon to select an existing QoS definition or create a QoS definition from the
      QoS list
      dialog. The
      QoS List
      option is disabled for the checkpoints that cannot generate QoS.
    • Use excludes:
      allows you to define objects to be excluded from monitoring. The probe uses regular expressions to search patterns that are excluded from the checkpoint.
    • Excludes list:
      allows you to specify the patterns to be excluded in the checkpoint. Click the
      Excludes list
      ( single_arrow.png ) icon to specify existing patterns or define pattern in the
      Exclude list
      dialog. You can define objects that you do not want to monitor in the template checkpoint.
    • (
      From version 5.10
      for the
      tablespace_free
      checkpoint)
      Enable Threshold on Space:
      enables you to define another threshold value for the
      tablespace_free
      checkpoint. If you select this option, the probe evaluates the values specified in both the
      Threshold value
      and
      Threshold Value for Space (In GB)
      fields before generating an alarm for threshold breach.
    • Check Interval:
      specifies the interval after which the database is scanned. If specified, this value overrides the profile
      Check Interval
      .
      Reduce this interval to generate alarms and QoS frequently. A shorter interval can also increase the system load.
    • Samples:
      specifies the number of samples to calculate an average value. This average value is compared to the specified alarm threshold.
      Default: 1
      When the probe starts, the average value from the number of available samples is calculated. For example, if you specify the
      Samples
      value as 3, the probe performs the following actions:
      • uses the first sample value in the first interval
      • uses the average of samples 1 and 2 in the second interval.
    • Scheduling:
      allows you to refine the time interval of profile that runs on the server. Use this option if you do not want to use the
      Run interval
      time. For example, run your profile to monitor the server only on Wednesday mornings at 8:00 A.M. You can select any of the following:
      • rules:
        defines rules to run the schedules of the template checkpoint.
      • exceptions:
        defines exceptions to run the schedules of the template checkpoint.
    • (From version 5.30)
      Send Alarm
      : specifies the probe to generate alarms when the checkpoint breaches the defined threshold.
    • Clear message:
      specifies the message used when the specified threshold is not breached.
      Default: default_1
    • Clear severity:
      specifies the severity of the clear message.
      Default: clear
  10. (If
    Scheduling
    is selected) Create a schedule.
  11. Create a hint text in the
    Hint Editor
    tab, as required.
  12. Save the definition and restart the probe to use the checkpoint.
The checkpoint is created.
Stored Procedure Support in creating custom checkpoint (probe versions 5.4 and above):
The probe supports the use of stored procedures in creating custom checkpoints. Checkpoint query can include any stored procedure with one output parameter argument which is of type SYS_REFCURSOR.
Example
: If the stored procedure name is get_data_resultset with one out parameter of type SYS_REFCURSOR, then the custom check point query using the stored procedure should be “BEGIN  get_data_resultset(:1); END;”
Add QoS Definition
You can define the QoS to be used in the checkpoint. You can send QoS values to the QoS database.
Follow these steps:
  1. Click the
    QoS List
    ( single_arrow.png ) icon on the
    Edit template checkpoint [checkpoint name]
    dialog.
  2. Right-click on this list and select
    New
    .
  3. Enter a name and description of the QoS metric that you want to define. The name of the QoS has to start with the checkpoint name.
  4. Specify the following information:
    • Name:
      specifies the name of the Quality of Service message.
    • Description:
      specifies additional information about the QoS message.
    • Unit:
      specifies the unit of QoS metric.
    • Abbreviation:
      specifies the abbreviated name of the QoS metric.
    • Metric:
      selects the required QoS metric.
    • Max Value:
      specifies the maximum value of the QoS metric.
  5. Click
    OK
    .
  • To modify a QoS definition, right-click on it and select
    Edit
    .
  • To delete a QoS definition, right-click on it and select
    Delete
    .
  • To copy the attributes of a QoS definition to another, select
    Copy
    .
Add Exclude Patterns
You can specify the patterns to be excluded in the template checkpoint. Excludes are defined using regular expression patterns.
Follow these steps:
  1. Click the
    Excludes list
    ( single_arrow.png ) icon on the
    Edit template checkpoint [checkpoint name]
    dialog.
    The
    Excludes list
    dialog appears.
  2. Specify the regular expression in the
    Match expression
    dialog.
  3. Click
    Test
    to verify the defined exclude pattern. This test is possible only to run active profiles and checkpoints. The test uses the status list (on the Status tab) as input. If there already are active excludes, the matching objects are excluded from the status list before the test.
    When you click
    Test
    , an
    Excludes test
    list appears that shows the result of the test. Red text lines show the objects that are excluded using the tested pattern. The "object thresholds" function as an "include list". This means that if there are specific thresholds defined for a specific object, this object will always stay in, even if the exclude pattern would eliminate it typically. This is considered also in the test function.
  • To modify a pattern, right-click on it and select
    Edit
    .
  • To delete a pattern, right-click on it and select
    Delete
    .
  • To copy the attributes of a pattern to another, right-click on it and select
    Copy
    .
Define a Threshold
The threshold list contains the predefined set of monitoring parameters that you can use in your profiles. The probe allows you to modify the thresholds as required. The threshold values can be defined by modifying checkpoints in the respective profile. Every checkpoint must have at least one threshold, but you can define additional thresholds. The probe scans the entire server to verify any matching events. When any given event breaches the set threshold, the probe generates an alarm message. 
(From version 5.30)
The alarms on threshold values are generated based on the Severity instead of the threshold ID.
Example: you want to monitor available space in a tablespace using the
tablespace_free
checkpoint. As this checkpoint uses the <= operator, you can define the following threshold conditions when the available space is:
  1. <=10% with the
    critical
    severity
  2. <=20% with the
    warning
    severity
  • CA does not recommend you to delete the default checkpoints and the thresholds from the probe to avoid any missing alarms.
Follow these steps
:
  1. In the
    Thresholds / Schedules
    section of the
    Edit template checkpoint
    dialog, right-click and select the
    New
    option.
    The
    Edit Threshold
    dialog appears.
  2. Complete the following information:
    • Threshold object name
      : specifies the monitoring object name, if applicable. If you do not specify the object name, the probe uses the name as
      default
      . Some special checkpoints have a second threshold named count (for example, locked_users).
    • Threshold value
      : specifies the value used for threshold evaluation.
    • Current interval value
      : specifies the last measured value, if invoked from the status report.
    • Severity
      : specifies the severity of alarm message to be used for the threshold.
    • Message
      : specifies name of message used for threshold alarm.
    • Message text
      : specifies the message text, containing variables. If the message text is changed from a profile list, you must create new message.
    • (
      From version 5.10
      for
      tablespace_free
      checkpoint)
      Threshold Value for Space (In GB)
      : This field is enabled only if you select
      Enable Threshold on Space
      field in the Edit template checkpoint dialog. You can define one more threshold that the probe checks before generating an alarm. Example: you want an alert when the remaining tablespace free size is 20% and 20 GB of the total space. Follow these steps:
      1. Select the
        Enable Threshold on Space
        field on the Edit template checkpoint dialog.
      2. Specify the following values:
        • Threshold value:
          20%
        • Threshold Value for Space (in GB):
          20
      When the tablespace free size reaches both these values, the probe generates an alarm for threshold breach.
    • Variables
      : displays the list of variables that are available only for the custom checkpoints. For example, $check, $profile, $instance, $object, $state. The variables for every custom checkpoint are different, depending on the variable query.
  3. Click
    OK
    to save the threshold.
  • To modify a threshold, right-click on it in the Thresholds list and select
    Edit
    .
  • To delete a threshold, right-click on it in the Thresholds list and select
    Delete
    .
  • To copy the attributes of a threshold to another, right-click on it in the Thresholds list and select
    Copy
    .
  • The
    count_interval
    threshold in the
    invalid_objects
    checkpoint supports only the greater than (>) conditional operator.
Create a Schedule
You can specify a schedule to run a checkpoint. A schedule is the execution period of the checkpoint on specified days, time and date values. If you are using exceptions, the schedule is considered as an execution break.
If the schedules list is empty, the checkpoint is executed in every 24 hours. Additionally, there can be defined number of schedules for each checkpoint. These schedules define additional rules to the check interval or exceptions of it. The rules and exceptions cannot be mixed in one checkpoint.
  1. In the
    Thresholds / Schedules
    section of the
    Edit template checkpoint
    dialog, right-click and select the
    New
    option.The
    Schedule ID
    dialog appears.
  2. Specify the days of the week when the schedule is applicable.
  3. Specify the time range to execute the schedule in
    Time from
    and
    to
    fields.
  4. Specify the date range to execute the schedule in
    Date from
    and
    to
    fields.
  5. Select the frequency to execute the schedule:
    • Run once
      : indicates the probe to execute the checkpoint only once a day in the defined period.
    • Run interval
      : indicates the probe to execute the checkpoint at each monitoring interval in the defined period.
  6. Click
    OK
    to save the scheduling details.
  • To modify a schedule, right-click on it in the Schedules list and select
    Edit.
  • To delete a schedule, right-click on it in the Schedules list and select
    Delete.
  • To copy the attributes of a schedule to another, right-click on it in the Schedules list and select
    Copy.
View Profile Status
You can view the defined profiles and their corresponding checkpoint templates. You can also modify the properties of an individual checkpoint object.
Follow these steps:
  1. On the
    Status
    tab, select a profile in the right pane and navigate to the required checkpoint in the profile.
  2. Double-click an object in the right pane.
    The
    New Threshold
    dialog appears with the profile details.
  3. Specify the following information to modify the properties of a checkpoint object:
    • Threshold value
      : enables you to select the required threshold values.
    • Current interval value
      : enables you to select the required interval values. Click double_arrow.png to add the selected interval values to the Threshold values list.
    • Message
      : specifies the message that you want to generate.
    • Message text
      : specifies text of the message, containing variables. If the message text is changed from a profile list, you must create new message.
    • Variables
      : specifies the variables to be used in the message. Click double_arrow.png to add the selected variable in the message text.
    • Severity
      : specifies the severity of alarm message.
  4. Click
    OK
    .
(Optional) Rename Connection or Profile
(Valid on oracle probe version 5.0 and later) If you rename a connection or a profile, the probe shows two nodes for the same profile in UMP, and some data might be misplaced. To avoid this, you must restart the probe and run some queries in the database.
Follow these steps:
  1. Close and deactivate the
    oracle
    probe.
  2. Deactivate the
    data_engine
    probe in your IM.
  3. Execute the following queries in the database:
    update s_qos_data
    set ci_metric_id = null
    where probe = '?'
    The query updates the ci_metri_id column in the s_qos_data table with null value for the target probe entities.
  4. Activate the
    data_engine
    probe.
  5. Activate the
    oracle
    probe.
As the probe publishes QoS data, the
data_engine
probe updates the null values with the correct key values.
(Optional) Use Regular Expression
A regular expression (regex for short) is a special text string to describe a search pattern. Constructing regular expression and pattern matching requires meta characters. The probe supports Perl Compatible Regular Expressions (PCRE), which are enclosed within forward slash (/). For example, the expression /[0-9A-C]/ matches any character in the range 0 to 9 in the target string.
You can also use simple text with some wildcard operators for matching the target string. For example, *test* expression matches the text test in target string.
The probe uses regular expressions to search patterns that are excluded from the template checkpoint. For example, you are searching for the pattern, no_connection. Enter “/no_connection/” in the
Match expression
dialog and click
OK
. The probe searches for all the matching instances of the specified pattern.
The following table describes some examples of regular expression and pattern matching for the probe.
Regular expression
Type of regular expression
Explanation
.
Standard (PCRE)
Matches against any character
[A-Z]
Standard (PCRE)
Matches any uppercase alpha character
\d*
Custom
Matches for the name which starts from letter d
(Optional) Configure Message Pool
The
Message  pool
tab allows you to view the list of all alarm messages defined in the probe. You can right-click and select the required message to create, edit, copy, or delete alarm messages.
Follow these steps:
  1. Double-click the required message that you want to modify.
  2. Specify the following information:
    • Checkpoint:
      indicates the checkpoint for which the alarm message is generated.
    • Message text:
      specifies the required message text for the checkpoint.
    • Variables:
      selects the variables to be used in the message. Click double_arrow.png to add the selected variable in the
      Message text
      field.
  3. Click
    OK
    to save the message.
  • To modify an alarm message, right-click on it and select
    Edit
    .
  • To delete an alarm message, right-click on it and select
    Delete
    .
  • To copy the attributes of an alarm message to another, right-click on it and select
    Copy
    .