Knowledge Base

Handling PATROL Events Generated by Sentry KMs in BMC Helix Operations Manager

KB1268 - Jun 24, 2022

Type: Best practice

Description: How to receive and manage PATROL events generated by Sentry Software's KMs in BMC Helix Operations Manager(BHOM).

Additional Keywords: Helix, BHOM, Events

Related Topics

Introduction

Each time a threshold is breached:

  • Events of class 11 or 9 are generated by the PATROL Agent
  • STD_41 or specific PATROL events such as HardwareProblem, ConnectorProblem, StorageProblem, Studio, etc. are generated by the Sentry Software's KMs.

By default, the PATROL Agent does not send PATROL_EV events to BMC Helix Operations Managements. However, since the events generated by the Sentry Software's KMs provide more information about the actual problem, you may want to receive them in your BMC Helix Operations Management Events console.

In this article, you will learn how to:

  • force the PATROL Agent to send PATROL events to BMC Helix Operations Management Events
  • close the events of class 11 and leave the Sentry ones opened
  • allow OK events (p_class == 9) to close previous alarms.

Procedure

Forcing the PATROL Agent to send PATROL Events

To allow PATROL events of class PATROL_EV to be sent to Helix, add the following ruleset to your PATROL Agent through a monitoring policy or by using other tools such as pconfig, wpconfig, or PATROL Configuration Manager:

"/AgentSetup/integration/HelixMonitorEvents" = { REPLACE = "1" }
Enabling this option may result in a large amount of PATROL events to be sent. To prevent performance issues, it is strongly recommended to create additional event policies to handle the unwanted events.

Closing the events of class 11 and leave the Sentry ones opened

To close the events of class 11 and leave the Sentry ones opened, you need to create the following event policy in BMC Helix Operations Management:

class equals 'PATROL_EV' AND p_class equals '11' AND ( object_class has_prefix 'SEN_' OR object_class has_prefix 'SKM_' OR object_class has_prefix 'MS_HW' OR object_class has_prefix 'X_' )

as explained below:

  1. Connect to BMC Helix Operations Management
  2. Go to Configuration > Event Policies and configure the policy below:

    Keeping the events of `class 11`

  3. In the Policy Configuration pull-down list, click Advanced Enrichment and create this rule:

    Keeping Sentry events only

  4. Save your changes.

Allowing the events of class 9 to close alarms generated by Sentry KMs

To allow OK events (p_class == 9) to close the alarms generated by Sentry KMs, you need to create the following policy in BMC Helix Operations Management:

class equals 'PATROL_EV' AND ( p_class equals '9' OR p_class has_suffix 'Problem' OR p_class within '41,Studio' )
  1. Go to Configuration > Event Policies and configure the policy below:

    Having the OK events close the alarms

  2. In the Policy Coniguration pull-down list, click Advanced Enrichment and create these rules:

    Advanced Enrichment - Event Lookup

    Advanced Enrichment - Close Old Events

  3. Save your changes.