vdi.vmware
Introduction
Tags beginning with vdi.vmware identify events generated by VMWare Horizon View.
Valid tags and data tables
The full tag must have 4 levels. The first two are fixed as vdi.vmware. The third and fourth levels identify the type of events sent.
Technology | Brand | Type | Subtype |
---|---|---|---|
vdi | vmware | horizon |
|
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
---|---|
vdi.vmware.horizon.agent | vdi.vmware.horizon |
vdi.vmware.horizon.console | vdi.vmware.horizon |
vdi.vmware.horizon.connection_server | vdi.vmware.horizon |
How is the data sent to Devo?
Define the following relay rules for each tag:
vdi.vmware.horizon.agent
Source port | Customer source port, for example |
---|---|
Source data |
|
Target tag |
|
Sent without syslog tag | ✓ |
Stop processing | ✓ |
Â
vdi.vmware.horizon.console
Source port | Customer source port, for example |
---|---|
Source data |
|
Target tag |
|
Sent without syslog tag | ✓ |
Stop processing | ✓ |
Â
vdi.vmware.horizon.connection_server
Source port | Customer source port, for example |
---|---|
Source data |
|
Target tag |
|
Sent without syslog tag | ✓ |
Stop processing | ✓ |
Â
Table structure
This is the set displayed by this table.
Field | Type | Extra fields |
---|---|---|
eventdate |
| Â |
acknowledged |
| Â |
application_id |
| Â |
desktop_id |
| Â |
endpoint_id |
| Â |
event_id |
| Â |
event_type |
| Â |
folder_path |
| Â |
group_id |
| Â |
lun_id |
| Â |
machine_id |
| Â |
module |
| Â |
node |
| Â |
session_id |
| Â |
severity |
| Â |
source |
| Â |
thinapp_id |
| Â |
time |
| Â |
user_disk_path_id |
| Â |
user_sid |
| Â |
module_and_event_text |
| Â |
rawMessage |
| ✓ |
hostchain |
| ✓ |
tag |
| ✓ |
Â