EventTracker filter

The EventTracker filter is a Java™ class that can log all client events that are sent to the Tivoli®'s process automation engine. You can use the EventTracker filter to track the overall usage of application and identify the causes of potential issues.

After you enable the EventTracker filter, events are written to the *_clientevents.log in the WAS appserver ROOT\profiles\profile\maximo\logs directory, where

By default, the logging level for the EventTracker filter is set to INFO, which logs all events. To narrow the focus of logged events, you can set the logging level to ERROR, and then specify a specific user, application, or combination of user and application. If you set the logging level to ERROR and do not specify a user or application, then only error events are logged.

The EventTracker filter does not log exceptions. However, you can compare the timestamps in the error log to the EventTracker log to locate the potential causes of exceptions. Log entries are written in a tab-delimited format so you can import the log file into a spreadsheet application.

The EventTracker filter logs the following information:

Log item Explanation Example value
Time The time that the event was received. 09/30/11 08:56:01.015
Duration The time in milliseconds that was used to handle the event. 37
Server The hostname combined with the IBM Maximo® Asset Management server name. localhost-MXServer
User The user name of the user who sent the request. wilson
MAXSessionID The session ID for the user. 734
UISessionID The user interface (UI) session ID for the request, which includes a number in parenthesis to indicate the total number of UI sessions the user has. 1(1)
App The ID of the application that was used to send the request. The total number of applications in memory for a given UI session is listed in parenthesis next to the application ID. wotrack(1)
Page The ID of the page that the user had open when the event was sent. mainrec
Sequence The sequence value that was sent with the request. Multiple events can be sent in a single request, so if multiple logged events have the same sequence value, they were part of the same request. 2|1
Event The client event that was sent to the server. click
Target Control The ID of the control that was the target of the event. toolactions_
button_0
Target Component The ID of the component that was the target of the event. toolactions_
button_0- toolbarbutton_
image
Value The value of the event. wotrack
mxevent When the click event is sent to the server, the mxevent provides additional information to explain the actual event that occurred. For example, when the user clicks on a Save button, the mxevent records that the event was sent to save the data. INSERT
additionalevent The additional event, if one was sent with the event.  
additionaleventvalue The additional event value, if one was sent with the event.  


Feedback