The Formatted Events Catalog

Those wishing to analyze audit trail data or develop audit trail reports may do so using the option to have CyberAudit-Web export audit trail data to a separate database. An ODBC or JDBC connection may then be made to the database with third party programs such as Crystal Reports.

If this option is set, audit events stored in the CyberAudit-Web database will be periodically formatted and written to the specifed catalog(database). Names of keys and locks associated with the events are looked up, as are various enums used internally to make the data more readable.

The database specified cannot already exist, it will be created and populated with tables. Clicking Reload clears all data from the formatted events database and causes CyberAudit-Web to re-process audit trail data from the beginning.

Data is written periodically and a maximum of 100 events will be written per minute. Because of this, the data in the formatted events catalog may not be up to date.

There are currently four reporting tables:

Table	Description
Events	Contains audit trail data from CyberLocks and CyberKeys formatted with names, dates, and times. Dates and times will be rendered to the time zone of the top level subsystem.
key_comm_log	Captures information related to the key communications log.
lock_comm_log	CyberLock status information captured when downloading a CyberLock.
report_audit_events	This table mirrors the audit_events table used by CyberAudit-Web. It contains all audit trail data from the CyberAudit-Web system. Dates and times are not formatted or rendered to a time zone.

Events table

Column Name	Data Type	Description
event_id	integer	A unique identifier
personnel_id	integer	A unique identifier for the key's owner
personnel_name	string	The name of the key's owner
key_id	string	The key's id (K00000000)
key_name	string	The key's name (or mission name if a mission)
lock_id	string	The lock's id (L00000000)
lock_name	integer	The lock's name
videx_time	integer	Time of the event (seconds since 1996 UTC)
event_date	datetime	Time of the event (a datetime rendered to the server's timezone)
event_type	integer	An integer enum (-2 to 58)
event_type_str	string	A description based on the event type
event_from_key	boolean	Was the event from a key (as opposed to a lock)?
recstamp	integer	Time the event was recorded
lock_set	boolean	Was the lock configured by this contact?
lock_downloaded	boolean	Was the lock downloaded by this contact?
key_timezone	string	Timezone the key was last configured in
key_offset	integer	Offset from UTC (in seconds) that the key was last configured in
mission_id	string	If the event was generated by a mission
invalid_date	boolean	Indicates whether the date and time for the given event_date was reliable based on whether the "clock stopped" flag was set

Top

key_comm_log table  

Column Name	Data Type	Description
key_id	String	The key's id (K00000000).
mission_id	String	The mission id (M00000000) if the contact was made during a mission.
key_name	String	The current name of the key.
personnel_id	integer	A unique identifier for the key's owner.
personnel_name	string	The name of the key's owner.
key_videx_time	integer	Time of the key's configuration (seconds since 1996 UTC). Based on the key's clock.
key_datetime	datetime	Time of the key's configuration (a datetime rendered to the server's timezone). Based on the key's clock.
key_tz	String	Java TimeZone ID used by the key, if any. Either key_tz or key_offset will be used.
key_offset	integer	The offset from UTC used by the key in minutes, if any. Either key_tz or key_offset will be used.
communicator_id	String	The ID of the communicator used to configure the key.
communicator_name	String	The name of the communicator used to configure the key.
keypad_id	String	The id of the keypad used (t00000000) if the key was programmed at an Authorizer.
keypad_name	String	The name of the keypad used. If the key was programmed at an Authorizer.
communicator_videx_time	integer	Time of the key's configuration (seconds since 1996 UTC). Based on the communicator's clock.
communicator_datetime	datetime	Time of the key's configuration (a datetime rendered to the server's timezone). Based on the communicator's clock.
communicator_tz	String	Java TimeZone ID used by the communicator, if any. Either communicator_tz or communicator_offset will be used.
communicator_offset	integer	The offset from UTC used by the communicator in minutes, if any. Either communicator_tz or communicator_offset will be used.
download_videx_time	integer	Time that the key's configuration was recorded (seconds since 1996 UTC). Based on the server's clock.
download_datetime	datetime	Time that the key's configuration was recorded (a datetime rendered to the server's timezone). Based on the server's clock.
millivolts	integer	Battery voltage of the key.
number_of_events	integer	Number of events that were downloaded from the key.
comm_error	integer	An enumeration of error codes (0 is no error).
comm_error_str	String	A string representing the error code.

Top

lock comm log table

---

Column Name	Data Type	Description
lock_id	String	The lock's id (L00000000).
lock_name	String	The current name of the lock.
download_videx_time	integer	Time that the lock's download was recorded (seconds since 1996 UTC). Based on the server's clock.
download_datetime	datetime	Time that the lock's download was recorded (a datetime rendered to the server's timezone). Based on the server's clock.
download_key_id	String	The id of the key used to download this lock (K00000000).
download_key_name	String	The current name of the key used to download this lock.
access_count	integer	The number of times that the lock has been accessed.
download_count	integer	The new number of events that were downloaded.
lockspec_id	integer	The most recent configuration used to program the lock (a reference into the h_lockspecs table).

Manage System Context Help Articles