Node v0.9 compatible
Log errors and stack traces in Sentry from within your Node.js applications.
All processing and sending happens asynchronously to not slow things down if/when Sentry is down or slow.
- 0.6.x
- 0.8.x
- 0.9.x (latest unstable)
$ npm install raven
var raven = require('raven');
var client = new raven.Client('{{ SENTRY_DSN }}');
client.captureMessage('Hello, world!');
client.captureError(new Error('Broke!'));
client.captureMessage('Hello, world!', function(result) {
console.log(client.getIdent(result));
});
client.captureError(new Error('Broke!'), function(result) {
console.log(client.getIdent(result));
});
Note: client.captureMessage
will also return the result directly without the need for a callback, such as: var result = client.captureMessage('Hello, world!');
If you really care if the event was logged or errored out, Client emits two events, logged
and error
:
client.on('logged', function(){
console.log('Yay, it worked!');
});
client.on('error', function(){
console.log('oh well, Sentry is broke.');
})
client.captureMessage('Boom');
Optionally declare the DSN to use for the client through the environment. Initializing the client in your app won't require setting the DSN.
Optionally set the name for the client to use. What is name?
new raven.Client(dsn[, options])
client.captureMessage(string[,callback])
client.captureError(Error[,callback])
You can find me on IRC. I troll in #sentry
on freenode
.