My web application sets the session ID in either a cookie or a query string variable. How do I configure Urchin?
Web applications usually use a session identifier need to monitor the session ID to insure state during the userÂ’s session. Traditionally this session ID has been stored on the userÂ’s machine in a cookie. Sometimes, when users have cookies turned off, the web application adapts to the situation and appends the session ID to all requests sent to the server. Typically the session ID is attached to the request query. This can cause problems for Urchin especially if youÂ’re using the Session ID tracing method.
The problem is that Urchin can only look for the application defined session ID in one location. So, if your application is setting the session ID in two locations, based on the userÂ’s browser settings, Urchin will not be able to accurately count the total number of sessions.
The solution for this is to process all of your logs with a script that places the session ID in the URL or in a cookie. Then, when you configure your profiles, you can specify the location of the session ID and be sure it will exist in that location.