2.9.00 enhancements

The following are the changes in the 2.9.00 release of BMC PATROL for Event Management:

Overriding of threshold and/or poll time

In version 2.9.00 of BMC PATROL Knowledge Module for Event Management, if threshold and/or poll time is configured for an application class of a Knowledge Module, through BMC ProactiveNet Central Monitoring Administration (CMA), Event Management KM threshold and poll time rules are not applied to same application class if it is created or already present.Instead, Event of class ESG_INFO is generated.

If a parameter is deactivated from Event Management KM threshold rule and the threshold and/or poll time CMA policy is present for same application class, parameter is deactivated through EM KM threshold rule and the CMA rules are not applied, but Event of class ESG_INFO is generated.

To avoid generation of ESG_INFO events, set the value of the following variable to 1:

/AS/EVENTSPRING/CMA/disableEvents

Timeout and retry capability on Patrol agent TCP port connections

You can now specify timeout and retry options for the TCP connections to monitor availability target from availability server through AS_AVAILABILITY application class.  For more details about RFE https://communities.bmc.com/ideas/3323. To increase the number of retries, modify the value of the following configuration variable:

/AS/EVENTSPRING/AVAILABILITY/tcpRetries

Special characters in instance names

You can now monitor application instances which contain special characters in the names, while applying threshold or poll times rules. See the following example:

"/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/NT_PRINTER/hp_==__deskjet_5100/PrStatus" = { REPLACE = "1,1 0 3 0 0 0,1 1 2 1 2 1,1 2 3 0 0 2" }

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*