ESX
ESX: The primary function of ESX is to partition a physical server into multiple virtual machines (VMs), allowing different operating systems to run simultaneously and improving hardware utilization.
To onboard such a source to Axoflow, complete the generic appliance onboarding steps.
Labels
Axoflow automatically adds the following labels to data collected from this source:
| Analytics label | Message field | value |
|---|---|---|
vendor |
meta.vendor |
broadcom |
product |
meta.product |
esx |
service |
meta.service.name |
vmk, lsud, vsan, iofiltervpd, hostd, cmmdstimemachine, vmware, vpxa, eam, rhttpproxy, sdrsInjector, fdm, esxupdate, healthd, ConfigStore, kmxa, crx-cli, backup.sh, configStoreBackup, Host, vmauthd, localcli, watchdog-vsanperfsvc, watchdog-iofiltervpd, apiForwarder, tmpwatch, .etc.init.d.vsanmgmtd, ComplianceManager, hostprofiletrace, vobd, ucs-tool-esxi-inv, usbarb, auto-backup, cmmdsTimeMachineDump |
You can use the labels as:
- Filter labels on the Analytics page,
- in the Filter By Label field during log tapping.
You can use the message fields
- in Flow Processing steps, for example, in the Query field of Select Messages steps,
- in AQL expressions in the search bars.
Sending data to Splunk
When sending the data collected from this source to Splunk, Axoflow uses the following sourcetype and index settings:
| source | sourcetype | index |
|---|---|---|
vmware:esxlog:<service-name> |
vmware:esxlog:<service-name> |
infraops |
The service-name in the source and sourcetype is the same as the service label, for example, vmware:esxlog:vmware
If the Axoflow classification doesn’t set the source field for the message automatically, and you haven’t set it in a flow processing step manually (by setting the meta.destination.splunk.source field), AxoRouter automatically sets the source to the name of the AxoRouter connector that received the message (for example, axorouter-syslog-tcp-514).
Sending data to Google SecOps
When sending the data collected from this source to a dynamic Google SecOps destination, Axoflow sets the following log type: VMWARE_ESX.
Sending data to Microsoft Sentinel
When sending the data collected from this source to a Microsoft Sentinel destination, Axoflow normalizes the data and sends it to the following table: Syslog.
Earlier name/vendor
- VMware ESX