Metric "Syslog.global.logHost" not collected on Hosts Systems in VCF Operations 9.1.0

Products

• VCF Operations

Issue/Introduction

• Following an upgrade to VCF Operations 9.1.0, the metric Syslog.global.logHost is not collected for ESXi host system objects.
• In the VCF Operations UI, navigating to Properties > Configuration > Security > Remote log host shows a value of none, even if the setting is correctly configured on the ESXi host.
  
• Compliance Alert Definitions (e.g., ISO compliance or default security alerts) trigger warnings or mark the host as non-compliant because the expected log host value is missing.

Environment

VCF Operations 9.1.0

Cause

This issue has been identified as a product defect in the VCF Operations 9.1.0 GA build. The data collection mechanism fails to correctly pull the Syslog.global.logHost property from the host system object following the 9.1 upgrade.

Resolution

Resolution

Engineering has identified the root cause and a fix is merged into the main code branch.

• Fix Version: This issue is expected to be resolved in the 9.1.1 release.
• Workaround: There is currently no UI-based workaround to force the collection of this specific metric in version 9.1.0. If compliance reporting is critical, users may need to temporarily suppress or modify the specific symptom definition for the log host until the upgrade to 9.1.1 is performed.

Additional Information

Download Broadcom products, patches and software