Network Management

Orion Log Viewer and Orion Log Analyzer Alert Integration Is Not Working Properly

This article is created to address the issue where OLV\OLA are not able to parse correct data based on the trap varbinds received and there is a delay in triggering alert based on OLV\OLA rules.

First published date

6/8/2022 5:39 AM

Last published date

6/8/2022 5:39 AM

Overview

OLV\OLA is not able to parse correct trap varbinds value if the trap is received consecutively under the same source node and same OID within a 1-minute interval.

Receiving the trap consecutively under the same source node and the same OID within a 1-minute interval also has a delay in executing the trigger action.

Product section

Network Performance Monitor

Cause

By design, OLA/OLV rules integration with Orion Alerting uses a cache that is by default set to 1minute.

The cache is in place to prevent overload of alerting in case of heavy traffic Syslog or Traps.

Resolution

  1. Login to the web console
  2. Access the Advanced Configuration settings in the Orion Web Console.
  3. Look for "RuleAlertQueueItemExpiration" setting
  4. Change the value to 00:00:00 and then save the setting.
Changing the value of "RuleAlertQueueItemExpiration" to 00:00:00 means data caching is removed.