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

winston-loggly-transport

v1.0.3

Published

A Loggly transport for winston

Downloads

39

Readme

LogglyTransport

A Loggly transport for winston, with support for bulk log posts.

Usage

LogglyTransport may be installed via npm:

npm install --save winston-loggly-transport

You can register LogglyTransport like any other winston transport:

const winston = require('winston');
const LogglyTransport = require('winston-loggly-transport');

// using the default logger
winston.add(LogglyTransport, {
  token: 'yourLogglyToken',
  subdomain: 'your-loggly-subdomain'
});

// or, with a new logger instance:
const logger = new winston.Logger({
  transports: [
    new LogglyTransport({
      token: 'yourLogglyToken',
      subdomain: 'your-loggly-subdomain'
    });
  ]
});

// Log like normal:
logger.info('A message to send to Loggly', { 
  some: { meta: 'data' }
});

Options

The following options are available for LogglyTransport:

// All options are optional, unless otherwise marked
new LogglyTransport({
  // Your Loggly API token (required)
  token: 'yourLogglyToken',

  // Your Loggly subdomain (required)
  subdomain: 'your-loggly-subdomain',

  // Tags to apply to all logs
  tags: [],

  // Messages logged within this time period (ms) 
  // will be sent together in bulk
  bufferInterval: 1000,

  // If there are this many messages
  // in the buffer, they will be sent together in bulk
  // (even if bufferInterval is not yet complete)
  bufferSize: 100,

  // If set to true, no messages will be sent to Loggly
  silent: false,

  // Minimum level at which messages 
  // will be sent to Loggly
  level: null
});

Comparison to winston-loggly

This library was built as an alternative to winston-loggly, to overcome a few issues in that library:

  • winston-loggly does not support bulk requests
  • winston-loggly is missing test coverage of basic behavior, making new development by an outside developer tricky.

On the other hand, this library is missing some behavior provided by winston-loggly:

  • winston-loggly-transport does not yet support non-bulk requests
  • winston-loggly-transport does not yet support tags on individual logs (because in bulk requests, only one set of tags may be specified for all logs)
  • winston-loggly-transport does not yet support HTTP authorization
  • winston-loggly-transport does not yet accept unique input names
  • winston-loggly-transport does not yet support the winston streaming api.
  • winston-loggly-transport does not yet support the winston query api.