#439 Unique identification for events coming from the same FastFix client
Each sensor collects a different userIdentification value in Espigon trials. For example:
The value of userId for "HttpRequestOnServerSide" events is "esp_acom" (the application user)
The value of userId for "DBStatementEvent" events is "sql-query-execution-logger" (hardcoded in the sensor?)
*The value of userId for "DbErrorEvent" events is "ccalle" (the system user)
It's necessary that all context events contain the same value for userIdentification field ( for each user of FastFIx), since this field is used by event correlation component in order to group the events depending on the user, and then correlate them correctly.
In case that this field (userIdentification) is not the proper one, the event correlation system needs a field that is shared by all the events coming from the FF client, independent from platform, application and sensor.
One possible suggestion would be using (ClientId), in case userIdentification is not possible.
Former ticket Nr. 688
