Foglight Experience Monitor (FxM) and Foglight Experience Viewer (FxV) systems don't match up on time-wise for user sessions. For example, on FxV a session runs from 9:27 to 10:29. But, for FxM, the time stamp is 9:27 – 9:41.
We see the same 'Session Key' in FxM as the 'Session ID' we are looking at in FxV. How could there be a discrepancy between what FxM considers to be a session versus what FxV considers to be a session? We thought what FxV considers a Session is all defined from within FxM.
Even though FxM does determine the session id for FxV, each system has its own rules for when a session stops. FxM has a session timeout and a session stop page setting. FxV has a session timeout and a session stop event as well.
You can have multiple sessions with the same session id. They are differentiated by the session start time. In other words, both FxV and FxM can have multiple sessions with the same session id (or key). These sessions will just have different start and end times. Because each system has its own rules for stopping the session, you can get multiple sessions on FxV that are a single session on FxM and vice versa.
To get the sessions to sync up better:
1. Make the FxM and FxV timeout settings all the same:
a. adjust the FxM 'User Session timeout period' on the 'Configure' | 'Monitoring' | 'User Sessions' page in the FxM web console UI.
b. adjust the FxV 'Timeout For "Short" Sessions' on the 'Configure' | 'Hit Analysis' | 'Hit Analysis Configuration Options' page in the FxV web console UI.
c. adjust the FxV 'Timeout For "Long" Sessions' on the 'Configure' | 'Hit Analysis' | 'Hit Analysis Configuration Options' page in the FxV web console UI.
2. Do not have a session stop page defined in FxM or a session stop event defined in FxV.
a. Don't have any 'Logout Patterns' configured on the 'Configure' | 'Monitoring' | 'User Sessions' page in the FxM web console UI.
b. Don't have a "Default Stop Session Event" on the 'Configure' | 'Transaction Filters' page in the FxV web console UI.
c. Don't have a 'Stop Session Event' configured for any of your individual Transactions.
FxV does have two timeouts (short and long). The reason behind that is that if you have a user who hits your home page (for example) and doesn't continue on you may want to timeout that session faster.
Here is a list of issues that we're aware of concerning sessions getting of out sync:
1. FxV uses different time out values so FxV and FxM will start and stop sessions at different times which means that an FxM session may be split across multiple FxV sessions or it may be a part of a larger FxV session or both.
2. FxV has a “StopSession” event which can be defined by the user which causes same issue as #1.
3. FxM has a “logout page” feature which causes same issue as #1.
4. FxV can have hit filters defined which drop hits that may be listed in the FxM session log.
5. FxM can have filters defined that exclude hits from being sent to FxV but are included in FxM analysis or vice versa.
6. FxM puts all non-sessionized hits in a session by client ip. These aren’t sessions on FxV.
For example, why would there be multiple FxV sessions with the same session id (that are differentiated by the session start time)? That could be because sessions are being cut off early in FxV compared to FxM. So the session in FxM just keeps on trucking, considering the hits as part of a single session, with its same old 'Session Key' (aka in FxV as 'session id'). And, because FxV had stopped considering the hits it is getting as part of the previous session, it starts up a new session. And FxV gets its session Id's from FxM. So in FxV, the hits show up as a new session but with the same session id as the previous session.
Another example is that FxM can easily stop a session before it ends in FxV. Since the session id is the same, these additional hits go into the same session in FxV (because its still active) while FxM has started a new session.