...
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tags | Data tables | Ingest with collector | |||||
---|---|---|---|---|---|---|---|---|
Workday |
|
|
| |||||
|
|
| ||||||
|
|
|
For more information, read more About Devo tags.
...
You can use the Workday collector to send events to your Devo domain. If you use it, events will be sent to , but only for the app.workday.user_activity.activity
data table. Learn more about this in this article.
Table structure
These are the fields displayed in these tables:
Anchor | ||||
---|---|---|---|---|
|
Field | Type | Extra fields |
---|---|---|
eventdate |
| |
system_account |
| |
task |
| |
target |
| |
request_time |
| |
activity_category |
| |
email_address |
| |
ip_address |
| |
user_agent |
| |
hostchain |
| ✓ |
tag |
| ✓ |
rawMessage |
| ✓ |
Anchor | ||||
---|---|---|---|---|
|
...
workday.audit
Field | Type | Extra fields |
---|---|---|
eventdate |
| |
hostname |
| |
Task |
| |
Instances_Updated |
| |
Processed_Transaction |
| |
By_User |
| |
Business_Objects_that_Changed |
| |
hostchain |
| ✓ |
tag |
| ✓ |
rawMessage |
| ✓ |
Anchor | ||||
---|---|---|---|---|
|
Field | Type | Field transformation | Source field name | Extra fields | ||
---|---|---|---|---|---|---|
eventdate |
|
|
| |||
hostname |
|
|
| |||
user_agent |
|
|
| |||
activity_action |
|
|
| |||
task_display_name |
|
|
| |||
task_id |
|
|
| |||
request_time |
|
|
| |||
ip_v4 |
|
| ip | |||
ip_v6 |
|
| ip | |||
session_id |
|
|
| |||
device_type |
|
|
| |||
system_account |
|
|
| |||
at_devo_pulling_id |
|
|
| |||
hostchain |
|
|
| ✓ | ||
tag |
|
|
| ✓ | ||
rawMessage |
|
|
| ✓ |