Changes between Version 5 and Version 6 of PlugIns/GenericEvents/generic-event-monitor

Timestamp:

10/04/17 13:04:44 (7 years ago)

Author:

pharms

Comment:

--

PlugIns/GenericEvents/generic-event-monitor

@@ -75 +75 @@
 == Monitoring Applications ==
 
+To monitor an application, it must be equipped with an interceptor for events. This interceptor must transform the events into JSON messages as the one shown above and sent these messages to the port opened by the monitor. The monitor will then extract the messages and store the data in the log files.
 
+The log files are separated in the log directory by the application id as well as by the client id. This means, the interceptor must ensure, that application and client id are as unique as required by further analysis. A client id may for example be unique for a certain installation of an application on a certain host. But it may also be unique for a certain user. This depends on which information about the user is available at runtime of the monitored application.
 
-Log files are separated in the log directory by the URL of the monitored web application as well as by a unique id of the client. Please note, that a client here is a specific installation of a specific browser on a specific machine. If the installation changes, the client id may change. If several users use the same installed browser, they are considered as one user. To check if the monitor correctly records user actions, you can check if a specific log file is created in the log directory. Furthermore, you can check the {{{console.log}}} for respective messages, e.g. the following one:
+To check if the monitor correctly records user actions, you can check if a specific log file is created in the log directory. Furthermore, you can check the {{{console.log}}} for respective messages, e.g. the following one:
 {{{
   handled message of 12345 for app BlaBliBlup (5 events)