Skip to main content

jQuery ajax error logging on the server with log4net

This post is based on Toby Gundry's post on the same technique, but adapted for logging jQuery ajax errors (although I added a few extra things too).

In your Javascript:

        ajaxError: function (event, jqXHR, ajaxSettings) {
            var err = "Location: " + document.location.href + "; ";
            if (jqXHR)
                err += "Status: " + jqXHR.status + "; ";
                err += "Text: " + jqXHR.statusText + "; ";
            if (jqXHR.responseJSON) {
                err += "Message: " + jqXHR.responseJSON.Message + "; ";
                err += "Stack Trace: " + jqXHR.responseJSON.StackTrace + "; ";
            if (ajaxSettings) {
                err += "Data Sent: " + + "; ";
                err += "URL: " + ajaxSettings.url + "; ";
            var message = btoa(err);
            var log = new Image();
            log.src = "/JSLogger.ashx?error=" + message;
            //display some kind of friendly error message to the user

I used the btoa function for base64-encoding the content, but it's quite possibly unnecessary.  Anyway, make a JSLogger handler, something like this:

    public class JSLogger : IHttpHandler
        private static readonly ILog Log = LogManager.GetLogger(typeof(JSLogger));

        public void ProcessRequest(HttpContext context)
            string encodedError = context.Request.QueryString["error"];
            byte[] bytes = Convert.FromBase64String(input);
            string error = Encoding.ASCII.GetString(bytes); //using Unicode seems to have weird effects

                string name = "Username: " + context.User.Identity.Name;
                error += name;
            catch(Exception e){} //in case the username isn't available

        //IHttpHandler boilerplate omitted

Let me know if you have any ideas for improvement!


Post a Comment

Popular posts from this blog

Using Log4Net to use both event log and a rolling log file

Here's the config section, note that the applicationNameproperty in the EventLogAppender needs to be the same as the event source in the windows event log that you want to log to.  If the event source doesn't exist, that appender won't work.  In this particular project I create that during install using WiX (which is covered in another post)

    <appendername="RollingLogFileAppender"type="log4net.Appender.RollingFileAppender">      <filevalue="log.txt" />      <datePatternvalue="dd-MM-yyyy" />      <appendToFilevalue="true" />      <locationinfovalue="false" />      <rollingStylevalue="Size" />      <maximumFileSizevalue="1MB" />      <maxSizeRollBackupsvalue="10" />      <staticLogFileNamevalue="true" />      <layouttype="log4net.Layout.PatternLayout">        <conv…

Using WiX to create an event source during install of a .NET framework project

Edit: so I guess I wasn't the only one confused with this stuff, as it's been my most popular post by far!  If I've helped you out or saved you some time, please let me know in the comments :)

In order for this to work, you have to add references to WixUtilExtension and WixNetFxExtension to your WiX project.  Once that's done, add this inside a <Component> element:

<Util:EventSourcexmlns:Util=""Name="EVENTSOURCEGOESHERE"Log="Application"EventMessageFile="[NETFRAMEWORK40FULLINSTALLROOTDIR]EventLogMessages.dll" />
Obviously replace EVENTSOURCEGOESHERE with your event source name.  NETFRAMEWORK40FULLINSTALLROOTDIR is a property set by the WixNetFxExtension which stores the path to the .NET framework v4 directory, but you can replace this with the corresponding property for the directory containing the relevant EventLogMessages.dll file.  So if you're using the .NET framewo…

Umbraco Deployment Checklist

This is primarily aimed at deploying from Visual Studio to an Azure Web App + Azure SQL database, feel free to skip bits that aren't relevant if you're doing other things.

Prerequisites for developing locally:
Visual Studio (obviously)
Ensure IIS URL Rewrite module is installed using web platform installer (other downloads from MS documentation don't seem to work)

Set up Azure:
Make a new SQL Database in Azure, take note of the server name, database name, admin login and admin password.  If you already have a server and resource group, automate with Powershell as shown below (you'll need to replace the param values):
New-AzureRmSqlDatabase -DatabaseName "UmbracoDatabase" -ServerName "TheServer" -ResourceGroupName "Whatever" -Edition "Basic"
Add your IP to the Azure SQL db firewall so Umbraco can connect to it later when running locally
Create a new Azure web app, either manually or via Powershell:
New-AzureRmWebApp -ResourceGroupName…