cloud.vmware_tanzu

[ 1 Introduction ] [ 2 Tag structure ] [ 3 How is the data sent to Devo? ] [ 4 Table structure ]

Introduction

The tags beginning with cloud.vmware_tanzu identify events generated by VMware Tanzu.

Tag structure

The full tag must have 4 levels. The first two are fixed as cloud.vmware_tanzu. The third level identifies the type of events sent, and the fourth level indicates the event subtype.

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

Product / Service	Tags	Data tables

Product / Service	Tags	Data tables
VMware Tanzu Operations Manager	`cloud.vmware_tanzu.opsmanager.audit`	`cloud.vmware_tanzu.opsmanager.audit`

For more information, read more About Devo tags.

How is the data sent to Devo?

You can forward logs generated by Company using any Syslog drain (for example, Syslog-ng). Learn more about how to send VMware Tanzu logs and their structure here.

Table structure

These are the fields displayed in these tables:

cloud.vmware_tanzu.opsmanager.audit

Field	Type	Extra fields

Field	Type	Extra fields
eventdate	`timestamp`
hostname	`str`
timestamp	`str`
component	`str`
component_scheme	`str`
component_host	`str`
component_port	`int4`
result	`int4`
target	`str`
event_type	`str`
origination	`ip4`
forwarded_for	`ip4`
user_identification	`str`
uaa_authentication_mechanism	`str`
request_body	`str`
hostchain	`str`	✓
tag	`str`	✓
rawMessage	`str`	✓