Previous Topic

Book Contents

Book Index

Next Topic

Event Logging

Event Logging in Valuemation provides the possibility to collect information about how the application is being used. In contrast to standard Valuemation Log (which is still available), the data is stored in the database and displayed in catalogs and views. It can be filtered, grouped and otherwise processed as any Valuemation data. The data can also be analyzed by the Valuemation Analytics tool.

Event Logging makes it possible to observe and analyze user behaviour and the internal running of the application.
It provides answers to questions such as:

  • What catalogs, views or modules are used and in what context and order
  • What actions are used, how often, in what context and order
  • How long individual catalogs and views stay open
  • In what order the user switch between windows
  • How much time individual SQL statements, workflows, requests etc. take
  • What errors occur in the application, in what context the errors occur

The collected information can serve the following purposes:

  • Aid the design and development of the application
  • Optimize the GUI, increase application usability and improve user experience
  • Introduce predictive behaviour
  • Provide valuable input for the preparation of customer trainings
  • Aid testing of the application
  • Aid the support staff in resolving functionality issues

Event logging Concerns

  • Amount of collected data

    As event logging can potentially create a huge number of records, it is highly recommended to limit the amount of data by using the filters and thresholds provided in 'Application Monitoring Settings'.

    Moreover, the high cumulative potential of the data should be taken into account and the functionality treated accordingly. For example:

    • Event logging enabled only when the information will actually be used
    • Some kind of process, backup & delete policy adopted for the records

    Note that operations such as sorting or filtering may take some time. Overall, the value of this functionality lies in areas other than speedy performance.

  • User Privacy

    Event Logging is capable of collecting user-specific data including date/time information. Possible privacy concerns can, however, be solved by appropriate privacy settings.

Keywords

The following expressions may also be used in connection with Event Logging: Metadata Usage, Event Tracking, Usage Statistics, Usage Analysis.

In This Chapter

Event Logging Settings

Viewing Event Data

See Also

Application Monitoring

Console

User Sessions Logging

Log-Viewer