network.vmware
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 it is fixed as airwatch. Then, the fourth level identifies the subtype and is fixed as events.
Technology | Brand | Type | Subtype |
---|---|---|---|
network | vmware | airwatch | events |
Therefore, the only valid tag and table is:
- network.vmware.airwatch.events
How is the data sent to Devo?
To send events to Devo using this tag, you can use the Devo Relay and tag the events with network.vmware.airwatch.events. Learn how to install and configure the Devo Relay in this section.
Log samples
The following is a sample log of this technology:
<12>2021-01-01 01:00:30.000 localhost=127.0.0.1 network.vmware.airwatch.events: 15 20:42:43 AirWatch AirWatch Syslog Details are as follows Event Type: ConsoleEvent: AdminUserLoggedOutUser: sarahmoore@desktop-85.michell-taylor.comEvent Source: ServerEvent Module: AdministrationEvent Category: LoginEvent Data: LoginSessionID=bgfuquugflqgN/dev/contain/against/kyrgyz_republic/plan.webm Event Timestamp: January 15, 2021 20: 42:42
And this is how the log would be parsed:
Extra columns
Fields marked as Extra in the table below are not shown by default in data tables and need to be explicitly requested in the query. You can find them marked as Extra when you perform a query so they can be easily identified. Learn more about this in Selecting unrevealed columns.
Field | Value | Type | Source field name | Extra fields |
---|---|---|---|---|
eventdate |
|
| ||
host |
|
| vhost | |
event_type |
|
| ||
event |
|
| ||
user |
|
| ||
event_source |
|
| ||
event_module |
|
| ||
event_category |
|
| ||
event_data |
|
| ||
event_timestamp |
|
| ||
hostchain |
|
| ✓ | |
tag |
|
| ✓ | |
rawMessage |
|
|