Loupe - Log - Monitor - Resolve
Loupe / Developer's Guide / For .NET Framework / For ASP.NET MVC / Packaging and Sending Data / Reference - Sending Session Data Automatically
In This Topic
    Reference - Sending Session Data Automatically
    In This Topic

    The Loupe Agent supports two methods of automatically sending session data.  These methods can work together, but are designed for different situations.  You may want to use either or both of them in your application.

    1. Auto Send Sessions:  This is an option of the Server configuration that when enabled will have the agent periodically check for new sessions to send as well as automatically send the current process information when there is an error.  It supports the Loupe Server only, and can optionally remove information from the local computer when complete.
    2. Send Sessions On Exit This is an option that can be set on the Log object indicating that once the current process exists the Loupe Packager should send all new sessions.  It supports sending to Email and the Loupe Server, picking the Server in preference if it is configured and accessible. 
    If you are using a Loupe Server you will nearly always want Auto Send Sessions enabled.

    Comparing Options

    Auto Send Sessions

    Send Sessions On Exit

    Working Together

    These methods are designed to work together to cover the broadest range of user scenarios.

    Scenario One:  Immediately send sessions as soon as applications exit

    If you have configured Server integration this will be done automatically just by setting the AutoSendSessions option.  Otherwise, you can do this over email by setting the SendSessionsOnExit property each time the application starts.

    Scenario Two:  Sending error sessions

    If you have configured Server integration this will be done automatically just by setting the AutoSendSessions option.  Otherwise you can take advantage of the Log.MessageAlert event to both set the SendSessionsOnExit property and immediately send the partial (active) session in the event of an error.

    Scenario Two:  Sending error sessions when a user has declined to participate in your CEIP

    If you are providing an opt-out capability for your Customer Experience Improvement Program then some users will elect to not automatically send their data.   In the event of a problem they may change their minds and be willing to submit data.  If you are using the Loupe Error Manager the user will be able to simply check a box when faced with an error and enable SendSessionsOnExit.  This will then send their information this one time, enabling you to see both the immediate session that they were concerned about in full and the other sessions for your application that were still in the local repository (subject to your pruning limits). 

     

    See Also