net_connect alarms: Profile failed to execute in scheduled time interval

Document ID : KB000057333
Last Modified Date : 22/05/2018
Show Technical Document Details
Issue:
  • net_connect alarm messages: Profile failed to execute in scheduled time interval
  • Hundreds of alarms could be generated in a seemingly random fashion or after probe restart.

 
Environment:
net_connect probe 2.93 +
Cause:
  • The defined time interval is not long enough to execute all the defined monitoring profiles
  • This alarm was added to the probe in version 2.93
Resolution:
Follow the steps in the probe documentation to mitigate this

It is also possible to either filter out the alarms or reduce the severity of the alarms

Reducing alarm severity

  • 3.03 +
    • use the message pool manager in the probe config and change the severity of the alarm to the desired level
  • 2,93 +
    • create a nas rule to alter the severity
    • event.level = 2
      event.message = "Profile failed to execute in scheduled time interval"
      return event
    • nas pre-processing rule 'Message string' should be defined as:
    • ?? Profile * failed to execute in scheduled time interval

Filtering out the alarms

  • Create a nas pre processing rule with the following message filter in the config file
    • /.*Profile failed to execute.*/​

 
Additional Information:
If none of these solutions are suitable then you would need to downgrade to a lower version of the probe that does not create this alarm

e.g., 2.73