How to Resolve Persistent Failed-IOs-on-$(hostname) Alerts in VMware Aria Operations for Logs
search cancel

How to Resolve Persistent Failed-IOs-on-$(hostname) Alerts in VMware Aria Operations for Logs

book

Article ID: 451495

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

This article addresses persistent alerts in VMware Aria Operations that do not auto-cancel after the underlying I/O condition resolves, as well as redundant notification bursts. This typically occurs in environments integrated with VMware Aria Operations for Logs.

  • Periodically receiving active alerts in VMware Aria Operations or VMware Aria Automation.

  • Notification Event details show:

    VMware Aria Operations for Logs: Failed-IOs-on-ESXi_Hostname

  • These alerts remain open indefinitely and do not auto-cancel.

  • Corresponding events are not active or visible on the underlying vCenter Server instance.

 

Environment

 

  • VMware Aria Operations 8.18.x

  • VMware Aria Operations for Logs (formerly VMware vRealize Log Insight) 8.18.x

 

Cause

Alerts fail to clear due to two primary configuration deficits:

  1. Auto Cancel Disabled: The "Auto Cancel" feature is not enabled for the Failed-IOs-on-$(hostname) alert definition.
  2. Notification Heartbeat Active: The "Notification Heartbeat" is enabled, causing the system to trigger redundant notifications based on the adapter’s collection interval.

These notification events originate from log queries within VMware Aria Operations for Logs and are forwarded to Aria Operations via integration.

The alert definition Failed-IOs-on-$(hostname) does not automatically clear because the Auto Cancel feature is disabled by default for this specific alert definition in Aria Operations for Logs. Because the alert lacks an auto-cancellation trigger, Aria Operations retains the alert in an active state even after the underlying I/O condition resolves.

Resolution

  1. 1. Enable Auto Cancel

    1. Log in to the VMware Aria Operations for Logs UI with administrative privileges.
    2. Navigate to Alerts > Alert Definitions.
    3. Search for Failed-IOs-on-$(hostname).
    4. Click the alert definition to open it for editing.
    5. Enable the Auto Cancel setting.
    6. Click Save.

    2. Disable Notification Heartbeat

    1. Navigate to Alerts > Alert Definitions.
    2. Identify the notification rule associated with the alert.
    3. Edit the notification rule.
    4. Set "Notification Heartbeat" to Disabled/Inactive.
    5. Click Save.

    3. Manual Cleanup Existing active alerts created prior to these changes must be cleared manually:

    1. Navigate to Alerts > All Alerts in the VMware Aria Operations UI.
    2. Select and cancel the orphaned alerts.

Additional Information

  • Evaluation Window: Auto-cancellation occurs after the evaluation window passes (typically 10 to 15 minutes) without new matching log entries.
  • Downloads: See Download Broadcom Products and Software for product updates and releases.
  • Contact Support: To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.