HVR Alert Does Not Send Email Notifications for Capture Job Errors

Issue

An HVR email alert does not send notifications when a capture job is down, even though errors appear in hvr.out for channels included in the alert configuration.

The alert configuration file, $HVR_CONFIG/hubs/<hub_name>/alerts/<alert_name>.conf, includes the following setting: "Message_Error_Limit": 0

Environment

• HVR 6
• Alert type: Email notifications

Resolution

To resolve this issue, update or remove the Message_Error_Limit parameter in your alert configuration:

1. Open the alert configuration file: $HVR_CONFIG/hubs/<hub_name>/alerts/<alert_name>.conf
2. Find the Message_Error_Limit parameter and do one of the following:
   • Change the value from 0 to a positive number, such as 10.
   • Remove the parameter. The default value is 1000, which allows up to 1000 errors to be reported per scan.
3. Save the configuration.

If you still do not receive alerts, verify that the alert covers the correct channels and that relevant error messages exist in the scanned log window. For more information, see HVR Alert Properties - Message_Error_Limit.

Cause

This issue occurs when Message_Error_Limit is set to 0. This parameter controls how many alert messages the notification loop can send per scan. When the value is 0, we detect the errors but do not generate emails or events. The limit applies to the number of distinct errors detected, not the number of log lines for each error.