New! - Loupe Agent for JavaScript Released

Today we’ve published the Loupe Agent for JavaScript and we’re looking for people to help us put it through its paces!

The functionality has been broken into two separate and distinct pieces:

  • Client side - JavaScript agent that deals with logging
  • Server side - a HttpModule that receives the log messages

The JavaScript agent supports a lot of the functionality that you would expect from the normal .Net agent, providing different methods for logging (verbose, warning, etc) as well as ensuring that any unhandled exceptions are also recorded with as much information as we are able to capture client side.

When the JavaScript Agent wants to record information it sends it asynchronously to your web application to be integrated with everything else recorded by Loupe.  We’ve created an HttpModule to run with your application so any messages that are sent by the JavaScript agent are handled without the need to change any of your existing server code.

JavaScript Agent Data Flow

We will be expanding on the functionality in following blog posts, but you can get started right away: simply head over to NuGet and install the Http Module from here and then select either the Angular or native JavaScript agent from the GitHub repo.

We have also updated the Web Forms and Mvc/WebApi agents specifically to be able to utilise session Ids used by the HttpModule and JavaScript agent to allow you to track user activity client side and the corresponding server side processing.

Getting Started

Once you have the Http Module in place from NuGet and have the script referenced client side, then you want to start using it, assuming you’re using the native JavaScript agent you just need to add:

loupe.information("My Category", "My Caption", "My Description");

into your code (replacing the “My xxx” with your own meaningful text). When the JavaScript you have added to your code executes it will send a message to the server.

If you have either Loupe Desktop or Loupe Viewer running and showing live sessions you will see the message appear.

Its as simple as that, but If you can’t wait for futher posts and need more information immediately then the wiki for the JavaScript agent has a lot of information on how it works and how to use it.

What’s next?

As mentioned before we will be publishing more posts detailing the functionality in the agent, but for now we are eager to hear from anybody that does try the agent and get their feedback on it.

Related Posts

Loupe 4.5 Released with New Log Viewer for Web

Rapidly diagnose each error in any .NET application with our new Web Log Viewer and Exception root cause analysis, new in Loupe 4.5. New integration with Azure Service Bus and Azure Search enables full Loupe functionality without any Virtual Servers in Azure. Read more

Cloudflare Vulnerability Does Not Affect Us

The recently reported Cloudflare vulnerability where fragments of secure, encrypted user data could be exposed to a third party does not affect Gibraltar Software even though we use Cloudflare because we only route static content through the Cloudflare proxy for acceleration. Read more

We're out of our Last Data Center

Back in January of 2016 we decided to completely transition out of our data centers and into the cloud. On Sunday we finally shut down the last cluster of our hardware. Read more for how we did it and whether we would do it all over again if we had... Read more

Rock solid centralized .NET logging

Unlimited applications, unlimited errors, scalable from solo startup to enterprise.