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

node-cwlogger

v0.0.2

Published

A simple logger for writing to console and/or AWS cloudwatch using Winston 2.x

Downloads

6

Readme

Simple CloudWatch Logger

I wrote this because I do this sort of thing over and over. This module makes it easy (for me) to include this behaviour in many of my stack components.

Usage

const log = require( 'node-cwlogger' )( config );
log.info( 'Here we go!' );
log.error( new Error( 'you can not do that here!' ) );
log.debug( "No you don't!", err );
throw( "you gotta a problem" );

Configuration

const config = {
  includeNodeEnv: true,
  console: {
    enabled: true,
    level: 'error',
    colorize: true
  },
  cloudwatch: {
    enabled: true,
    level: 'debug',
    awsAccessKeyId: 'your key',
    awsSecretKey: 'your secret',
    awsRegion: 'your region',
    group: 'cloud watch group name',
    stream: 'cloud watch stream name'
  }
}

The AWS credentials will default (if not specified) to these environment variables:

  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_KEY
  • AWS_REGION

The CloudWatch group will default to process.env.NODE_ENV if not specified. The stream name is required, and would probably be the name of the application. The idea is to group multiple applications under their stack, so you can use something like awslogs and get logs like this to mix all of the apps in the stack together:

awslogs get staging ALL --start='1d ago' --timestamp --profile aws-profile-name

or to get just one app:

awslogs get staging "webserver*" --start='1d ago' --timestamp --profile aws-profile-name