Value Change domain
All changes tracked by the trigger-based value change application. This topic describes the domain's entities and attributes.
Available to roles: admin
Monitor Values Entity
A monitor values entity is created for each insert, update or delete recorded, contains the details of the change (table name, action, SQL text, etc.).
| Attribute | Description |
|---|---|
| Timestamp | Date and time the change was recorded on the Guardium® appliance. This timestamp is created during the data upload operation. It is not the time that the change was recorded on the audit database. To obtain that time, use the Audit Timestamp entity. |
| Timestamp Date | Date only from the timestamp. |
| Timestamp Time | Time only from the timestamp. |
| Timestamp Year | Year only from the timestamp. |
| Timestamp Weekday | Weekday only from the timestamp. |
| Server IP | IP address of the database server. |
| DB Type | Database type. |
| Service Name | Oracle only. Database service name. |
| Database Name | DB2®, Informix®, Sybase, MS SQL Server only. Database name. |
| Audit PK | For Sybase and MS SQL Server only. A primary key used to relate old and new values (which must be logged separately for these database types). |
| Audit Login Name | Database user name defined in the datasource. |
| Audit Table Name | Name of the table that changed. |
| Audit Owner | Owner of the changed table. |
| Audit Action | Insert, Update or Delete. |
| Audit Old Value | A comma-separated list of old values, in the format:column-name=column_value, |
| Audit New Value | A comma-separated list of new values, in the format:column-name=column_value, |
| SQL Text | Available only with Oracle 9. The complete SQL statement causing the value change. |
| Triggered ID | Unique ID (on this audit database) generated for the change. |
| Audit Timestamp | Date and time that the trigger was executed. |
| Audit Timestamp Date | Date portion of Audit Timestamp. |
| Audit Timestamp Time | Time portion of Audit Timestamp. |
| Audit Timestamp WeekDay | Day of week of the Audit Timestamp. |
| Audit Timestamp Year | Year of the Audit Timestamp. |
| Original Timezone | The UTC offset. This is done in particular for aggregators that have
collectors in different time zones and so that activities that happened hours apart do not seem as
if they happened at the same time when imported to the aggregator. For instance, on an aggregator that aggregates data from different time zones, you can see session start of one record that is 21:00 with original timezone UTC-02:00 and another record where session start is 21:00 with original timezone UTC-05:00, This means that these events occurred 3 hours apart, but at the same respective local time (9 PM). |
Changed Columns Entity
This entity describes a changed column.
| Attribute | Description |
|---|---|
| Changed Column Name | Name of the changed column on the database. |
| Old Value | Value before the change. |
| New Value | Value after the change. |
| Original Timezone | The UTC offset. This is done in particular for aggregators that have
collectors in different time zones and so that activities that happened hours apart do not seem as
if they happened at the same time when imported to the aggregator. For instance, on an aggregator that aggregates data from different time zones, you can see session start of one record that is 21:00 with original timezone UTC-02:00 and another record where session start is 21:00 with original timezone UTC-05:00, This means that these events occurred 3 hours apart, but at the same respective local time (9 PM). |