Enabling scope-based event grouping

The cloud native analytics component in your hybrid deployment disables any existing on-premises scope-based event grouping (SBEG) triggers during installation. However, the triggers that are related to enriching the ScopeID column and needed for scope grouping are not disabled. A specific set of triggers is added for cloud native analytics. Cloud native analytics creates scope-based groups, based on scope enrichment, and augments those groups with other groups from other analytics. The original SBEG triggers must remain disabled while cloud native analytics is active.

Procedure

  1. Check whether you already have scoping enabled on your on-premises ObjectServer. Run the following command.
    $OMNIHOME/bin/nco_sql -user username -password password -server server_name
    Where
    • username is the administrative user for the ObjectServer, usually root.
    • password is the password for the administrative user.
    • server_name is the name of your ObjectServer.
    Verify that:
    • A row is returned by the following query: select TriggerName from catalog.triggers where TriggerName='correlation_new_row';
    • The ScopeID field is present in the alerts.status table.
  2. To enable scope-based grouping, use the following steps:
    1. Follow the instructions in this link: https://www.ibm.com/docs/en/SSSHTQ_8.1.0/omnibus/wip/install/task/omn_con_ext_installingscopebasedegrp.htmlexternal link
    2. Download the file legacy_scoping_procedures.sql from here.
    3. Run the downloaded SQL file on your primary ObjectServer to update the triggers.
      $OMNIHOME/bin/nco_sql -server servername -user username -password password < legacy_scoping_procedures.sql
      Where
      • username is the administrative user for the ObjectServer, usually root.
      • password is the password for the administrative user.
      • server_name is the name of your primary ObjectServer.
    4. Run the downloaded SQL file on your backup ObjectServer to update the triggers.
      $OMNIHOME/bin/nco_sql -server servername -username username -password password < legacy_scoping_procedures.sql
      Where
      • username is the administrative user for the ObjectServer, usually root.
      • password is the password for the administrative user.
      • server_name is the name of your backup ObjectServer.