All important server actions, such as data access activity and stopping and starting the server, cause an event to be generated. Depending on which OpenAccess SDK profiles are active, the information generated by the event is displayed as it occurs on the runtime monitor and stored in a file named the event trace file. By default, the event trace file is located in the installdir/tracing directory, where installdir is your OpenAccess SDK Server installation directory.
By setting profiles in your OpenAccess SDK service configuration to control which events are traced, you can inspect information generated by these events. Event tracing allows you to monitor ongoing activity, troubleshoot problems, and fine-tune your data access infrastructure. For example, if you want to monitor the number of transactions an OpenAccess SDK Server processes for capacity planning purposes, you could set a profile in the service configuration to return only that information. In addition, the information stored in the event trace file is persisted, meaning that you can inspect the information at a later time.
Events are identified by:
An event ID
The service in which the event occurred
The time the event occurred
List of attributes and their values
Examples of information that can be monitored and traced are SQL statements, number of transactions, failures, and authentication information.
An event ID