What Firebug is for the client, Glimpse does for the server... in other words, a client side Glimpse into whats going on in your server.

Glimpse

A client side Glimpse to your server

Download Now

Remote Plugin

The Remote plugin is one of Glimpse's most powerful features. The plugin goes architecture has both client and server components. The plugin allows you to view requests from not only your own browser, but from other devices in any location. This allows for several interesting use cases, including mobile debugging, remote client debugging, tracking workflows, etc.

Usage

1) Watch		2) Select		Opt.) Rename
Watch the Client Session Panel for a client that you are interested in.		Once target client appears, select it and select the target clients request you are after.		At any time a can change your clients name by going to the following url and setting the name: http://yoursite.com/Glimpse/Remote, or http://127.0.0.1/Glimpse/Remote

Layout

Client Session Panel: List of available client session's
Client Request Panel: List of available client request's
Client Name: Name given to the session that is being tracked by Glimpse
Method: HTTP method used for the individual request (typically GET or POST)
Request URL: URL that can be used identity individual requests
Browser: Browser name that has been used for the request
Data/Time: When the request was made
Ajax: Whether the request was made via Ajax
Launch: Opens a given request as the current context
Count: Number of requests that are available to be viewed

A case study

Scenario
So your site works fine and is in production when you get a call from a user reporting a problem on a certain page. The same page works fine on your machine though.

Glimpse has a feature which allows you to look at the "debug information" for page requests made by other users and other machines. This is always helpful if you are debugging a site in a mobile browser where the Glimpse client panel is not usable.
Setup
- First you need to make sure that Glimpse is installed on the production site and turned on.
- Next you need to enable the IP address for the user who reported the problem. You user could tell you her address, but that may not actually be the public address used for the request. Point the user to http://www.prodcutionsite.com/glimpse/config , under "Your Settings" is the IP address that server sees. Add that IP address to the allowed addresses in web.config.
- In the current version, nothing prevents the user from clicking the 'eye' and see the debug information. If you have any data you rather not share with the user, turn that particular plugin off by using plugin blacklisting.
- Tell the user to click the "Set Glimpse Session Name" button on the same page. The user is then asked to specify a name. Their own name or company name would be a good choice. This also enables Glimpse on the user's browser.
- Now ask the user to load the problematic page again, she does not have to click on the Eye icon to see the Glimpse panel. That would just be confusing for most users.
Review remote requests
Now return to your own browser and open the production site as well. Click on the 'Remote' tab. On the right hand side you should see a list of different clients and the number of request that were monitored by Glimpse. In the 'Client' column you should see the name that was specified by the user. Click on 'Launch' next to it to show the requests for the client.

The remote tab behaves similar to the Ajax tab, you can 'Launch' one request to see the full data about that request. On the Request tab you can verify that the request was made by a remote client machine. You can further review the information to find out what may have caused the problem.

The Remote tab can also be helpful for local development. You can use different browsers to access your site and then compare the requests in one place.

Did you know

That you can configure how many requests your server will remember: To configure how many requests your server will hang onto you can simply adjust config as follows (note 15 is the default amount that we keep):
```
<glimpse enabled="true" requestLimit="5" />
```

Frequently Asked Questions

What happens when the maximum number of stored requests is reached (by default 15)?
Internally we store the requests in a FIFO Queue. This means that when the maximum number spaces in the queue are filled, we take the first one that was entered and remove it from the queue, thus making room for the new request.

Plugins

WebForms	MVC
Config - Summary of important stuff in your web.config Environment - Details of the server environment Request - What the server received in the request Server - Web server variables available for the request Session - Is using session, what is being stored Trace - Trace output for the request	Bindings - How MVC is binding the data Execution - What the execution pipeline looks like MetaData - MetaData associated with your View Model Routes - How routes are being evaluated Views - How MVC is finding the view that is being rendered
Meta
Timeline - Displays requestion timing information Ajax - Lets you dig into your Ajax requests Remote - View requests from a remote client