Managing thresholds by using BMC ProactiveNet with  adapters

Normally, BMC ProactiveNet must be used for events when it is configured to import data from PATROL or third party sources. This uses dynamic thresholds, which reduces false events, and generates all the events and abnormalities within BMC ProactiveNet. The probable cause analysis correlation can be used to isolate any probable causes related to the service events or violations.

Thresholds in PATROL or other third party products must not be set for the same parameters that are configured with thresholds in BMC ProactiveNet. Parameters that monitor up and down availability and error status such as Windows service status, database listener status, server up and down, and error conditions in log files must generate events in PATROL or other third party products. These parameters must not be trended in BMC ProactiveNet. Only the events for these parameters must be sent to BMC ProactiveNet for processing and probable cause analysis.