The team strives to make Glimpse installation and use as easy as possible, but sometimes things just don’t work out of the box. Here are some answers to problems you might encounter (but we hope you don’t).

npm fails to find the @glimpse packages!

Glimpse packages are not published to npm’s package feed. Instead, you must configure npm to use our beta package feed. If using a CI system or Cloud-hosting, you need to use an .npmrc file.

I don’t see the heads-up display (HUD) on my page or any browser activity in Glimpse for that request!

Here are a couple of things to check:

  • Make sure glimpse.init() occurs before any other package import (such as express). Also know that some transpilers can reorder your imports.
  • While all server requests should be captured by Glimpse, only Content-Type: text/html responses generated via Express res.send() will include a script that enables the Glimpse browser agent and heads-up display (HUD).

Alternatively, if the HUD still cannot be displayed, you can always launch the Glimpse client at <site>/glimpse/client.

I don’t see my request in the Glimpse client request history!

To reduce noise, the Glimpse client has a static filter that excludes certain requests from that list:

  • Requests for content other than documents (e.g. HTML or text) and data (e.g. JSON or XML)
  • Requests to Glimpse instrumentation endpoints
  • Requests for source map files
  • WebSocket requests

Requests do not arrive in real-time in the Glimpse client for my Azure application!

When hosting your application in Azure, you must configure the response buffer limit to ensure the Glimpse client can receive requests in real-time.

I don’t see all of the request or response body in the Glimpse client!

Glimpse captures request and response bodies up to a maximum size; if the body is larger it will appear truncated. You can increase the maximum size using configuration settings.