Custom commands implemented by any means may also be logged using the VBScript function AuditEvent.
Syntax
Sub AuditEvent(EventName As String, [ObjectName As String], [ActionArg1 As String], [ActionArg2 As String], [ActionArg3 As String])
|
Name |
Description |
|---|---|
|
EventName |
The name of the event that you want to add to the audit log database. |
|
ObjectName |
Optional name of the vault object upon which the custom event occurs. |
|
ActionArg1 |
Optional argument that describes the action taken. |
|
ActionArg2 |
Optional argument that describes the action taken. |
|
ActionArg3 |
Optional argument that describes the action taken. |
Remarks
The object specified by ObjectName must not be Nothing. The optional action arguments can be anything that you decide. Each argument should be one parameter of the action taken and should resemble the general pattern used by the built-in audit entries listed in Audited actions.
Related concepts
Related tasks
Configuring the audit log connection
Creating an audit log database
Localizing the audit log database
Installing the audit log viewer
Related information