Xdas Field Definitions - Novell XDASV2 - ADMINISTRATION GUIDE V1 Administration Manual

"properties":{
"Domain":{
"description":"A (URL) reference to the authority managing this
account.",
"type":"string"
},
"Name":{
"description":"A human-readable account name.",
"type":"string",
"optional":true
},
"Id":{
"description":"A machine-readable unique account identifier value.", -
EntryID
"type":"integer"
}
}
},
{
"id":"entity",
address details for the initiator
"description":"A representation of an addressable entity.",
"type":"object",
"properties":{
"SysAddr":{"type":"string","optional":true},
"SysName":{"type":"string","optional":true},
"SvcName":{"type":"string","optional":true},
"SvcComp":{"type":"string","optional":true},
}
}
B.2 XDAS Field Definitions
These fields in the schema are the XDASv2 fields defined specifically for audit events. Some or all
of these fields may also be relevant to other types of event, but information of this sort is required
for auditing services. The XDASv2 JSON record format is open. By that, we mean that any
additional fields may be added to the record at any place, as long as they don't conflict with the field
values defined for audit by the XDASv2 standard.
Thus, if there is a particular type of correlation data, such as a workflow identifier, or a session
identifier that can be used as correlation data points between events within a particular workflow or
client session, you may add these fields. Simply choose a non-conflicting name for your field.

XDAS Field Definitions

Table B-1
XDAS Field
Source (Optional)
36 Novell XDASv2 Administration Guide
/* lets take it as the partition?
Description
The source of an event identifies the event service of another system from
which this event was originally defined and converted to an XDAS event.
Since many events are generated directly by XDAS clients, the source field is
optional.
- Server details for Target, client
- DN