Anyone that is using the Webi audit tables (log to database) successfully, I would like to hear how you have dealt with the relationship (or lack thereof) between the event log (OBJ_A_EVENT_LOG) and log detail (OBJ_A_EVENT_DETL) tables.
The event log (OBJ_A_EVENT_LOG) contains the session value and an event log type ID. The type ID tells you what sort of event took place (logon, get a list of corporate documents, refresh, and so on). Also in the event log table is the event ID (A_EVLOG_N_ID).
In the event detail table there are four columns. One is the Event ID, which would seem to join to the Event Log table. One is the Object ID, which is the ID of the element (document, universe) in the repository. The 3rd is the object name (document name, universe name, object name…) used in the event. And last is the object type ID, which tells you that “Resort” is an “Object” and “Island Resorts Marketing” is a “Universe”.
So here’s the problem… the Event ID is not unique across sessions. So if my session has an event “10” that is a login, and your session has an event “10” that is a “get list of corporate documents”, then there is no way to track which event details go with each session.
There is a listing in the Webi docs that shows which event detail types go with each event type. For example, a Login does not have any event details, so that would allow me to fix the problem example for event “10” mentioned above.
For example, the event “Compute Result” has details “Repository Name”, “Universe Name”, “Document Name”, “Object Name”, and “Number of Lines”. So I added a table to my universe that restricts the join between the Event Log table and the Event Detail table to show only valid details for each event.
Still not good enough… there are sessions where the event ID is not unique, and the event type has the same details. Again, an example… my session has an event “20” which is “Edit Document”. Your session has an event “20” which is “Refresh Document”. Now when I run a report, I see two document names attached to my event, and two document names attached to your event.
So I am forced to conclude that the audit tables - at least at the detail level - are not going to provide correct information. Either that or I am missing something obvious. I hope I am missing something.
Can anyone that is using the audit tables shed some light on this? Feel free to email me off of the list if you like, and I will summarize and repost the results.
Regards,
Dave Rathbun
Integra Solutions
www.islink.com
Listserv Archives (BOB member since 2002-06-25)