Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Introduction

The tags beginning with network.vmware identify events generated by VMware.

Tag structure

The full tag must have four levels. The first two are fixed as network.vmware. The third level identifies the type of event sent, and the fourth level identifies the subtype.

These are the valid tags and corresponding data tables that will receive the parsers' data:

Product / Service

Tags

Data tables

VMware AirWatch

network.vmware.airwatch.events

network.vmware.airwatch.events

VMware NSX Advanced Load Balancer (Avi Networks)

network.vmware.nsx_avi.generic_event

network.vmware.nsx_avi.generic_event

VMware NSX Controller

network.vmware.nsx_controller

network.vmware.nsx_controller

network.vmware.nsx_controller.falcon

network.vmware.nsx_controller.falcon

VMware NSX Edge

network.vmware.nsx_edge

network.vmware.nsx_edge

network.vmware.nsx_edge.datapathd

network.vmware.nsx_edge.datapathd

network.vmware.nsx_edge.integrity_checker

network.vmware.nsx_edge.integrity_checker

VMware NSX Manager

network.vmware.nsx_manager

network.vmware.nsx_manager

network.vmware.nsx_manager.appl_proxy

network.vmware.nsx_manager.appl_proxy

network.vmware.nsx_manager.ccp

network.vmware.nsx_manager.ccp

network.vmware.nsx_manager.node_mgmt

network.vmware.nsx_manager.node_mgmt

network.vmware.nsx_manager.nsx_sha

network.vmware.nsx_manager.nsx_sha

VMware NSX’s other events

network.vmware.nsx_other

network.vmware.nsx_other

VMware Unified Access Gateway

network.vmware.uag.events

network.vmware.uag.events

For more information, read more About Devo tags.

How is the data sent to Devo?

Logs must be sent to the Devo platform via the Devo Relay to secure communication. See the required relay rules below:

network.vmware.nsx_controller.falcon

  • Source port - Any available port

  • Target tag - network.vmware.nsx_controller.falcon

  • Source message - .*comp="nsx-controller".subcomp="falcon".*

  • Stop processing - ✓

network.vmware.nsx_edge.datapathd

  • Source port - Any available port

  • Target tag - network.vmware.nsx_edge.datapathd

  • Source message - .*comp="nsx-edge".subcomp="datapathd".*

  • Stop processing - ✓

network.vmware.nsx_edge-integrity_checker

  • Source port - Any available port

  • Target tag - network.vmware.nsx_edge-integrity_checker

  • Source message - .*comp="nsx-edge".*subcomp="integrity-checker".*

  • Stop processing - ✓

network.vmware.nsx_manager.appl_proxy

  • Source port - Any available port

  • Target tag - network.vmware.nsx_manager.appl_proxy

  • Source message - .*comp="nsx-manager".subcomp="appl-proxy".*

  • Stop processing - ✓

network.vmware.nsx_manager.ccp

  • Source port - Any available port

  • Target tag - network.vmware.nsx_manager.ccp

  • Source message - .*comp="nsx-manager".*subcomp="ccp".*

  • Stop processing - ✓

network.vmware.nsx_manager.node_mgmt

  • Source port - Any available port

  • Target tag - network.vmware.nsx_manager.node_mgmt

  • Source message - .*comp="nsx-manager".*subcomp="node-mgmt".*

  • Stop processing - ✓

network.vmware.nsx_manager.nsx_sha

  • Source port - Any available port

  • Target tag - network.vmware.nsx_manager.nsx_sha

  • Source message - .*comp="nsx-manager".*subcomp="nsx-sha".*

  • Stop processing - ✓

network.vmware.nsx_other

  • Source port - Any available port

  • Target tag - network.vmware.nsx_other

  • Source message - .*comp="nsx-.*

  • Stop processing - ✓

Table structure

These are the fields displayed in these tables:

  • No labels