Vmware

LogZilla App Store application: Vmware

Overview

VMware vSphere is a virtualization and cloud computing platform that enables organizations to create, run, and manage virtual machines (VMs) and cloud-based services. It provides a complete virtualization infrastructure, including virtualized computing, networking, storage, and security resources.

vSphere enables multiple operating systems and applications to run on a single physical server or cluster of servers, allowing organizations to consolidate IT infrastructure and reduce hardware costs. Key features include High Availability (HA), Distributed Resource Scheduler (DRS), and Fault Tolerance (FT) for increased reliability and availability of virtualized applications.

App Function

The VMware vSphere app includes customized rules, dashboards, and triggers designed specifically for vSphere environments.

Performance Configuration Required:

The app can extract 123 possible user tags from vSphere log messages. While all tags are enabled by default, it is strongly recommended to enable only the tags of interest and disable the remainder, as each tag has a performance cost.

Configuration Steps:

  1. Edit /etc/logzilla/apps/vmware/config/vmware-config.yaml
  2. In the DESIRED_USER_TAGS section, list only the tags you need
  3. Remove unused tag entries to optimize performance
  4. Refer to USER_TAG_DEFINITIONS section for tag descriptions

Vendor Documentation

Incoming Log Format

VMware vSphere uses standard syslog format with two distinct message structures used simultaneously:

Format 1:

  1. Date-timestamp
  2. Severity level
  3. Process name and ID
  4. Key-value pairs
  5. Message text

Format 2:

  1. Date-timestamp
  2. Thread ID
  3. Key-value pairs
  4. Event ID
  5. Message text

The VMware app can parse both formats to extract user tag information.

Parsed Metadata Fields

These are the fields / user tags that are parsed from the log messages:

vSphere User Tag NamevSphere User Tag Name
vmw_config_typevmw_device_changed
vmw_esx_shell_commandvmw_esx_shell_user
vmw_esxi_auditvmw_esxi_auth_failed_source
vmw_esxi_auth_failed_uservmw_esxi_auth_source
vmw_esxi_auth_typevmw_esxi_auth_user
vmw_esxi_cli_commandvmw_esxi_connect_source
vmw_esxi_connectivity_componentvmw_esxi_drs_from
vmw_esxi_drs_tovmw_esxi_drs_vm
vmw_esxi_esxupdate_commandvmw_esxi_firewall_operation
vmw_esxi_firewall_rulesetvmw_esxi_hostd_auth_user
vmw_esxi_iscsi_servervmw_esxi_nfs_datastore
vmw_esxi_nfs_servervmw_esxi_nfs_status
vmw_esxi_nsx_severityvmw_esxi_permission_event
vmw_esxi_portgroupvmw_esxi_problem
vmw_esxi_problem_datastoresvmw_esxi_scsi_additional_sense_code
vmw_esxi_scsi_additional_sense_code_qualifiervmw_esxi_scsi_device_status
vmw_esxi_scsi_host_statusvmw_esxi_scsi_latency
vmw_esxi_scsi_plugin_statusvmw_esxi_scsi_sense_code
vmw_esxi_scsi_sense_datavmw_esxi_severity
vmw_esxi_snapshot_operationvmw_esxi_snmp_trap_name
vmw_esxi_snmp_trap_oidvmw_esxi_sub
vmw_esxi_uptimevmw_esxi_vim_datastore
vmw_esxi_vmdowntimevmw_esxi_vmfs_heartbeat_datastore
vmw_esxi_vmfs_volume_guidvmw_esxi_vmk_component
vmw_esxi_vmk_worldvmw_esxi_vmkernel_net_vm_name
vmw_esxi_vmotion_bandwidthvmw_esxi_vmotion_opid
vmw_esxi_vmotion_typevmw_esxi_vmotiondst_opid
vmw_esxi_vmprecopybandwidthvmw_esxi_vmprecopystuntime
vmw_esxi_vmsvmw_fdm_state
vmw_ha_componentvmw_ha_component_operation
vmw_ha_guesthbvmw_ha_slave
vmw_hataskvmw_hostd_vmotion_id
vmw_opidvmw_recordop
vmw_recordop_actionvmw_rsv_source
vmw_rsv_timevmw_scsi_path_state
vmw_scsideviceio_pidvmw_task_status
vmw_uservmw_vc_alarm_source
vmw_vc_alarm_statusvmw_vc_alarm_type
vmw_vc_api_invocationsvmw_vc_auth_failed_source
vmw_vc_auth_failed_uservmw_vc_auth_source
vmw_vc_auth_typevmw_vc_auth_user
vmw_vc_custom_field_namevmw_vc_custom_field_on_vm
vmw_vc_drs_migrate_clustervmw_vc_drs_migrate_datastore
vmw_vc_duplicate_ip_vm1vmw_vc_duplicate_ip_vm2
vmw_vc_fdm_statevmw_vc_file_action
vmw_vc_mks_hostvmw_vc_msg_info
vmw_vc_msg_vmvmw_vc_power_host
vmw_vc_power_statusvmw_vc_power_vm_name
vmw_vc_reconfig_onvmw_vc_rhttpproxy_error
vmw_vc_task_methodvmw_vc_task_object
vmw_vc_task_operationvmw_vc_task_status
vmw_vc_task_typevmw_vc_vmodl_fault
vmw_vc_vmotion_fromvmw_vc_vmotion_precopystuntime
vmw_vc_vmotion_tovmw_vc_vpxd_clientip
vmw_vc_vpxd_hearbeat_hostvmw_vc_vpxd_username
vmw_vim_fault_typevmw_vm_heartbeat_source
vmw_vm_heartbeat_statusvmw_vm_state_transition_post
vmw_vm_state_transition_prevmw_vm_vmx_name
vmw_vmfs_heartbeat_statusvmw_vmkernel_vmotion_id
vmw_vmotion_statusvmw_vob_component
vmw_vob_event_typevmw_volume_name
vmw_vsphere_op_time

Log Examples

Log Format 1 - Process-based

text
- - 2022-10-07T01:31:23.561Z info vpxd[06166] [Originator@6876 sub=Default opID=sps-Main-670825-661-106283-91] [VpxLRO] -- ERROR session[52209c62-c72c-38b9-47de-a9cde9fc032f]521ac939-f711-0fa9-41fc-62fad40b3af9 -- CatalogSyncManager -- vim.vslm.vcenter.CatalogSyncManager.queryCatalogChange: vmodl.fault.NotSupported

Log Format 2 - Thread-based

text
- - 2022-10-07T01:31:23.868Z [pool-24-thread-1] INFO  opId=sps-Main-670825-661 com.vmware.vim.storage.common.util.OperationIdUtil - OperationID present in invoker thread, adding suffix and re-using it sps-Main-670825-661-106283
Vmware | LogZilla Documentation