I'm working on a web app that's going to be rolling out to a few users for testing. There's obviously going to be bugs, so I'd like to capture them to make it easier to develop fixes. Is there a way for me to intercept any console messages (both browser/js errors and messages generated with console.log) in my web app, so I can send them to a logging service on the server and have them available for debugging?

I'm working on a web app that's going to be rolling out to a few users for testing. There's obviously going to be bugs, so I'd like to capture them to make it easier to develop fixes. Is there a way for me to intercept any console messages (both browser/js errors and messages generated with console.log) in my web app, so I can send them to a logging service on the server and have them available for debugging?

• javascript

Share Improve this question Follow edited Feb 9, 2013 at 1:47 ajsharma 1,18811 gold badge1010 silver badges1717 bronze badges asked Jul 26, 2011 at 18:49 sslepiansslepian 1,92155 gold badges2121 silver badges2727 bronze badges

Add a ment  | 

2 Answers 2

Sorted by: Reset to default 5

Yes.

Intercepting console.log() calls:

console['log'] = function(msg){
    // do wahtever you need with msg here
}

Intercepting errors (so called diaper anti-pattern):

try {
    // your app's code
} catch(err) {
    // do what you to do in case of error need here
}

Here is the proof: jsfiddle.

However, I would suggest creating your own function, that will handle console.log() purpose and could be switched off on production. Plus, it will work properly (that means: won't throw errors), when the browser does not support console.log() calls. This could look like that:

window['log'] = function(msg){
    if (typeof console != 'undefined' && typeof console.log != 'undefined'){
        console.log(msg);
    }
}

A little late... this may be an interesting read, just need to implement the method to send to the server, but that's trivial. Taking Over console.log