The previously mentioned issue refers to the fact that if you were to start a new monitor on each new connecting http session, then the created monitors would start degrading your performance, since the monitor is not designed to scale to a large number of instances per process. So for asp.net applications, we recommend that you start and stop the single instance of your IAnalyticsMonitor in the Global.asax class.
Generally speaking, the monitor will send and save data periodically and if you also call Stop on the monitor in the Application_End method of the Global.asax, the "final" data will also be stored to disk and resent on the next start. So in terms of data loss, you should not be concerned as long as the Stop method is called.
For your client, I am not sure if they run the two modes within the same IIS-site/process or in two different sites on the same server and if your issue is with the separation of data from the two modes? If you only need to track data in the "production" mode, you'll need to only call the Start method on the monitor if the application is started in that mode (however you determine that). If the monitor is not started, all tracking calls will be no-op, so you'll only need to create the conditional code in tour Global.asax file.
Don't know if I really answered your question with this. Let me know if you need further information...
Monitor web applications with the new EQATEC Application Analytics JS library. Compatible with all modern browsers.
Test it today >>