...
Introduction
The tags beginning with app.anaplan
identify events generated by Anaplan.
...
The full tag must have 4 levels. The first two are fixed asapp.anaplan
. The third level identifies the type of events sent, and the fourth level indicates the event subtype.
Technology | Brand | Type | Subtype |
---|---|---|---|
|
|
|
|
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
---|---|
|
|
Table structure
This is the set displayed in these tables:
Field | Type | Extra Label fields | |
---|---|---|---|
eventdate |
| - | |
hostname |
| - | |
id |
| ||
eventTypeId |
| - | |
userId |
| ||
tenantId |
| ||
objectId |
| ||
objectTypeId |
| - | |
objectTenantId |
| ||
additionalAttributes__actionId |
| ||
additionalAttributes__workspaceId |
| ||
message |
| ||
success |
| - | |
errorNumber |
| ||
ipAddress |
| - | |
userAgent |
| - | |
sessionId |
| - | |
hostName |
| ||
serviceVersion |
| - | |
eventDate |
| ||
eventTimeZone |
| ||
createdDate |
| - | |
createdTimeZone |
| ||
checksum |
| ||
hostchain |
| ✓ | |
tag |
| ✓ | |
rawMessage |
| ✓ |