The first part of all events logged to Nsure Audit is the component string. The intent of the component string is to facilitate queries across various products and events. For example, using wildcard characters, you can search for all iChain violations (\ichain\*\violations), all iChain events (\ichain\*), or violations from every logging application (*\violations).
Each logging application has its own set of components. The following sections list the components strings for Novell eDirectory, NetWare, and Audit the Auditor events. For information on other component strings, refer to the logging application’s product documentation.
The components for the eDirectory Instrumentation are as follows:
Table A-2 eDirectory Component Strings
Object |
Attribute |
Debug |
Misc |
Agent |
Connection |
Bindery |
Schema |
Partition |
Replica |
Meta |
|
These components are combined with the eDirectory Application Identifier (eDirInst) to form the component strings for all eDirectory events. For example,
eDirInst\Object eDireInst\Replica
The components for the NetWare Instrumentation are as follows:
Table A-3 NetWare Component Strings
File |
Directory |
Trustee |
Volume |
Module |
Network |
Connection |
Alert |
Server |
|
These components are combined with the NetWare Application Identifier (NetWareInst) to form the component strings for all NetWare events. For example,
NetWareInst\File NetWareInst\Network
The components for Nsure Audit Instrumentation are as follows:
Table A-4 Audit the Auditor Component Strings
Generic |
License |
Authentication |
Log |
Channel |
Configuration |
Heartbeat |
Engine |
These components are combined with the Nsure Audit Application Identifier (NsureAuditInst) to form the component strings for all Nsure Audit events. For example,
NsureAuditInst\Channel NsureAuditInst\Log