npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@findanyemail/winston-transport-stackdriver-error-reporting

v1.1.4

Published

Stackdriver Error Reporting transport for winston logger (Node.js).

Downloads

5

Readme

Stackdriver Error Reporting transport for Winston logger

Build Status Code Climate Scrutinizer Code Quality NPM Version

Overview

This package is Winston logger transport that sends errors to Stackdriver Error Reporting service.

It's able to work in two modes:

  1. Logging to stdout compatible with Google Container Engine;
  2. Logging via an API with a help of @google-cloud/error-reporting library.

Usage and Configuration

Simply add this to your Winston transports array:

    winston.configure({
      transports: [
        new StackdriverErrorReporting(options),
      ],
    });

This transport supports 100% same configuration options as @google-cloud/error-reporting library, and uses API transport by default. The only additional option is options.level that controls minimal log entry level that should be sent to Stackdriver.

If you want to use stdout logging mode, all you need is to switch mode and set your serviceContext:

    winston.configure({
      transports: [
        new StackdriverErrorReporting({
          mode: 'console',
          serviceContext: {
            service: 'my service',
            version: '1.0.0'
          }
        }),
      ],
    });

How it works

When log entry reaches this transport, it will search meta object of log entry for objects that looks like errors (with stack property defined). After that, all errors will be delivered to Stackdriver Error Reporting service.

If meta.context property is defined, it will be attached to error as it's context. Please see Stackdriver Error Reporting documentation for details.

Alternatives

Official package @google-cloud/logging-winston exists now, a winston transport for Stackdriver Logging, which can automatically report logged errors to Error Reporting.