Giter VIP home page Giter VIP logo

winston-sentry's Introduction

winston-sentry

Sentry transport for winston logger for node js

Follow this sample configuration to use:

var winston = require('winston'),
    Mail = require('winston-mail').Mail,
    Sentry = require('winston-sentry');

var logger = new winston.Logger({
    transports: [
        new winston.transports.Console({level: 'silly'}),
        new Sentry({
            level: 'warn',
            dsn: "{{ YOUR SENTRY DSN }}",
            tags: { key: 'value' },
            extra: { key: 'value' }
        })
    ],
});

If you want to use patchGlobal to catch all uncaught errors, simply pass it as option like this:

new Sentry({
    patchGlobal: true
});

Winston logging levels are mapped to the default sentry levels like this:

{
    silly: 'debug',
    verbose: 'debug',
    info: 'info',
    debug: 'debug',
    warn: 'warning',
    error: 'error'
}

You can customize how log levels are mapped using the levelsMap option:

new Sentry({
    levelsMap: {
        verbose: 'info'
    }
});

Changelog

0.2.1

  • Changelog updated. No code changes.

0.2.0

  • Upgrade Raven client to version 1.1.x

0.1.5

  • Added license file. No code changes.

0.1.4

  • Bug fix: Level in log function should not fallback to the level filtering configuration

0.1.3

  • Fixes #30: Transport should not ignore configured log level

0.1.2

  • Upgrade Raven client to version 0.11.0
  • Refactoring global tags support to better work with the new client
  • Refactoring default options

0.1.1

  • Added support for global tags that will be added to every message sent to sentry

0.1.0

  • Upgrade Raven client to version 0.8.1

0.0.6

  • Error stack traces will be sent to sentry. See #3 for more details.
  • Upgrade raven to latest version (0.6.3)
  • Raven client can be passed to the transport from the outside

0.0.5

  • Winston metadata will be populated into the "Additional Data" section in Sentry.
  • If metadata contains a tags property, any key/value pairs within that property will be populated as Sentry tags. It will be removed from the "Additional Data" section to avoid data duplication. This will allow Winston metadata to be filterable within the Sentry UI.
logger = new winston.Logger(...);
logger.log("info", "my log message", {
      userInformation: {
         os: "linux",
         browser: "chrome",
         userAgent: "<user agent string>"
      }
      tags: {
         productVersion: "1.2"
      }
   }
});

// In Sentry, the "Additional Data" section would show:
// - userInformation
//      - os: linux
//      - browser: chrome
//      - userAgent: <user agent string>
//
// The tags would show:
// - level: info
// - logger: [logger property from transport constructor - defaults to "root"]
// - server_name: [machine name]
// - productVersion: 1.2

0.0.4

  • Added support for capturing "Additional Data".

0.0.3

logger = new winston.Logger(...);
logger.sentry_client.captureQuery("SELECT * FROM users;");
  • when logging as error level, it will implicitly call raven's captureError which will also capture the stack trace.
  • the winston.Logger object exposes the sentry client as sentry_client. Usage is simple:

** TODO:

  • capture sentry identifiers?

winston-sentry's People

Contributors

charsleysa avatar dhritzkiv avatar erlichmen avatar guzru avatar jb55 avatar mattrobenolt avatar niftylettuce avatar peter-barrett avatar scommisso avatar shaharke avatar yannickcr avatar zeekay avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

winston-sentry's Issues

Add fatal level

Add fatal level to error support.

Would be nice to change, the message too.

Let me know if you are open to pr.

Support for stack traces

Currently, there is no way to provide error objects in a way that will preserve stack traces in sentry.

For pinpointing production errors, that would be great (and is supported by raven-node).

Update to support Raven > 2.0.0

This package isn't working properly for me with Sentry version 8.2. (each error is reported to sentry but they are reported as a regression of a previous error even though they arent related.)

The raven dependency should be updated to version ^2.0.0

Cannot use with new version of SENTRY DSN format?

Can i use this module with new version of SENTRY DSN format?
Because, i get an error with new DSN format.
But it works with old style DSN.

2018-08-24 16:46 +09:00: [email protected] alert: failed to send exception to sentry: HTTP Error (401): Invalid api key
2018-08-24 16:46 +09:00: Cannot talk to sentry. Reason: Invalid api key

Additional data in winston.log() call ignored.

In winston I can do this: logger.error('Some error message', { someProperty : data });

However, when this is wired to the winston-sentry transport, 'someProperty' is discarded at some point.

multiple transports ?

I'm facing a situation where I need multiple instances of the transport, to customize the tags each level logged would have. Do you plan to support multiple transports ?

Latest code version is not deployed to NPM?

Hi,

I've installed the library using NPM and while the version seems to be the latest (i.e. 0.0.4), the code is different than what I see in GitHub:

Installed lib code:

this._sentry.captureError(new Error(msg), extra, function(err) {

Code in GitHub:

this._sentry.captureError(msg, extra, function(err) {

Notice that in GitHub, a new Error object is not created on top of the passed message (which is ok in case an Error is passed)

Log Level seems to be ignored

Hey guys,

I'm currently using winston-sentry in an express application, like below:

var logger = new winston.Logger({
    transports: [
        new WinstonSentry({
            level: 'error',
            dsn: '{{ MY_DSN }}'
        })
    ],
    exceptionHandlers: [
        new winston.transports.File({
            filename: '{{ MY_FILENAME }}',
            json: false
        })
    ],
    exitOnError: false
});

Whenever I call logger.info() the passed message will be send to Sentry despite the mismatch concerning the log level.

Have you got any hints?
Thanks!

Update the changelog

The changelog within the README.md file only goes up to 0.1.2 and the latest release is 0.1.5.

Can the missing details be filled in please.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.