cef0.airWatch

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

Introduction

The tags beginning with cef0.airWatch identify events in CEF format generated by AirWatch.

Tag structure

Events in CEF format don't have a specific tag structure, as explained in Technologies supported in CEF syslog format. They are always sent to a table with the structure cef0.deviceVendor.deviceProduct.

In this case, the valid data tables are:

Tags	Data tables

Tags	Data tables
`cef0.airWatch.airWatch`	`cef0.airWatch.airWatch`

How is the data sent to Devo?

Learn more about CEF syslog format and how Devo tags these events in Technologies supported in CEF syslog format.

Table structure

These are the fields displayed in this table:

cef0.airWatch.airWatch

Field	Type	Source field name	Extra fields

Field	Type	Source field name	Extra fields
eventdate	`timestamp`
hostname	`str`
priorityCode	`str`
cefTag	`str`
cefVersion	`str`
embDeviceVendor	`str`
embDeviceProduct	`str`
deviceVersion	`str`
signatureID	`str`
name	`str`
severity	`str`
_cefVer	`str`
cat	`str`
rt	`timestamp`
cs1Label	`str`
cs2Label	`str`
cs2	`str`
in	`int8`
out	`int8`
dvc	`ip4`
suser	`str`
cs1	`str`
msg	`str`
eventId	`str`
modelConfidence	`str`
eventAnnotationAuditTrail	`str`
customerID	`str`
agt	`str`
originalAgentHostName	`str`
Severity	`str`
aid	`str`
av	`str`
originalAgentVersion	`str`
eventAnnotationEndTime	`str`
eventAnnotationManagerReceiptTime	`str`
originalAgentId	`str`
originalAgentType	`str`
locality	`str`
eventAnnotationModificationTime	`str`
priority	`str`
customerURI	`str`
originalAgentAddress	`str`
at	`str`
originalAgentMacAddress	`str`
deviceZoneURI	`str`
dtz	`str`
eventAnnotationStageUpdateTime	`str`
eventAnnotationVersion	`str`
atz	`str`
deviceSeverity	`str`
deviceZoneID	`str`
assetCriticality	`str`
ahost	`str`
mrt	`str`
relevance	`str`
eventAnnotationFlags	`str`
art	`str`
originalAgentZoneURI	`str`
amac	`str`
hostchain	`str`		✓
tag	`str`	cefTag	✓
rawMessage	`str`