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

bunyan-eventlog

v1.0.1

Published

Bunyan stream for Windows Event Logs

Downloads

2

Readme

Windows Event Log stream for Bunyan

A simple Windows Event Log stream for Bunyan.

Installation

npm install bunyan-eventlog

Basic Usage

var bunyan = require( 'bunyan' );
var bunyanEventLog = require( 'bunyan-eventlog' );

var _systemLogger = {
    'src': false,
    'name': 'systemLogger',
    'serializers': bunyan.stdSerializers,
    'streams': [ {
        'level': 'info',
        'stream': new bunyanEventLog()
    } ]
}

var logger = bunyan.createLogger( _systemLogger );

logger.info( {
    'id': 999,
}, 'bunyan-eventlog test successful' );

Options

By default, bunyan-eventlog writes to the APPLICATION log, with a source of bunyan-eventLog.

When configuring the bunyan-eventlog stream, there are two options that control what data is included in your event log message: exclude and showExclude. By default, a Bunyan message contains a fair amount of additional data, beyond your message. Using the test.js script, Bunyan generates a message with the following information:

{
  "name": "systemLogger",
  "hostname": "myHostname",
  "pid": 18848,
  "level": 30,
  "id": 999,
  "showExclude": true,
  "exclude": [
    "time",
    "v"
  ],
  "msg": "bunyan-eventLog test successful",
  "time": "2018-05-14T20:24:19.435Z",
  "v": 0
}

You have the option of excluding any or all of the fields from the output message by adding exclude to either the logger definition, or at the time of generating the log message.

To make the change to the logger at a global level, you would do something like this (note the new bunyanEventLog line):

var _systemLogger = {
    'src': false,
    'name': 'systemLogger',
    'serializers': bunyan.stdSerializers,
    'streams': [ {
        'level': 'info',
        'stream': new bunyanEventLog( { 'exclude': 'all' } )
    } ]
}

If you do not want to exclude all of the items, you can exclude specific items by using exclude as an array, listing the fields to exclude from the final message:

var _systemLogger = {
    'src': false,
    'name': 'systemLogger',
    'serializers': bunyan.stdSerializers,
    'streams': [ {
        'level': 'info',
        'stream': new bunyanEventLog( { 'exclude': [ 'time', 'v' ] } )
    } ]
}

This can also be performed at the time of logging an event:

logger.info( {
    'id': 999,
    'exclude': 'all'
}, 'bunyan-eventlog test successful' );

or...

logger.info( {
    'id': 999,
    'exclude': [ 'time', 'v' ]
}, 'bunyan-eventlog test successful' );

You also have the option of showing the exclusion list by passing showExclude: true to either the initial logger definition, or to the logged event.

Any items not excluded are combined using a semi-colon separated join() and appended to the log message. Again, using the test.js script, the resulting event log message would look like this:

bunyan-eventLog test successful -- name: systemLogger; hostname: myHostname; pid: 18848; level: 30; id: 999; showExclude: true; exclude: time,v; msg: bunyan-eventLog test successful

Note

All of the usual event log message rules apply. For example, the event ID must be between 1 - 1000.