app.workday

Introduction

The tags beginning with app.workday identify events generated by Workday applications.

Valid tags and data tables

The full tag must have at least 3 levels. The first two are fixed as app.workday. 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
Workday	`app.workday.activity`	`app.workday.activity`
	`app.workday.audit`	`app.workday.audit`
	`app.workday.user_activity.activity`	`app.workday.user_activity.activity`

For more information, read more About Devo tags.

How is the data sent to Devo?

You can use the Workday collector to send events to your Devo domain. If you use it, events will be sent to 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:

app.workday.activity
app.slack.audit
app.workday.user_activity.activity

app.workday.activity

Field	Type	Extra fields
eventdate	`timestamp`
system_account	`str`
task	`str`
target	`str`
request_time	`str`
activity_category	`str`
email_address	`str`
ip_address	`ip4`
user_agent	`str`
hostchain	`str`	✓
tag	`str`	✓
rawMessage	`str`	✓

app.slack.audit

Field	Type	Extra fields
eventdate	`timestamp`
hostname	`str`
Task	`str`
Instances_Updated	`str`
Processed_Transaction	`str`
By_User	`str`
Business_Objects_that_Changed	`str`
hostchain	`str`	✓
tag	`str`	✓
rawMessage	`str`	✓

app.workday.user_activity.activity

Field	Type	Field transformation	Source field name	Extra fields
eventdate	`timestamp`
hostname	`str`
user_agent	`str`
activity_action	`str`
task_display_name	`str`
task_id	`str`
request_time	`timestamp`
ip_v4	`ip4`	ip4(ip)	ip
ip_v6	`ip6`	ip6(ip)	ip
session_id	`str`
device_type	`str`
system_account	`str`
at_devo_pulling_id	`str`
hostchain	`str`			✓
tag	`str`			✓
rawMessage	`str`			✓