Understanding vCenter Log Source Configuration in VCF Operations for Logs
search cancel

Understanding vCenter Log Source Configuration in VCF Operations for Logs

book

Article ID: 461300

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • The vCenter log source configuration appears to be missing or failed to propagate.
  • After configuring log collection within VCF Operations, the expected syslog forwarding settings are not visible in the vCenter Server Appliance Management Interface (VAMI).
  • Users are unable to identify or verify the log forwarding destination within the standard "Syslog" or "Log Collection" sections of the vCenter VAMI.
  • The absence of these configuration entries leads to uncertainty regarding whether log forwarding to the VCF Operations for Logs environment is active and functioning correctly.
  • When searching or troubleshooting within the VCF Operations interface, vCenter Server and ESXi log entries are visibly indexed and displayed under Operate > Logs > Analyze Logs.

Environment

  • VCF Operations for Logs 9.1.1
  • vCenter 9.x

Cause

This is expected behavior. VCF Operations for Logs utilizes the integrated Log Insight Agent within the vCenter appliance to forward logs directly. This process operates independently of the standard syslog configuration entries found in the vCenter VAMI.

Resolution

  • Verify log flow directly in the VCF Operations for Logs UI by navigating to Operate > Logs > Analyze Logs > Search for Logs for the affected vCenter.
  • Data transmission can also be verified via packet trace on port 9543 using a packet sniffing tool.