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

binder-logging

v1.0.3

Published

Module for consistent logging across Binder components

Downloads

6

Readme

binder-logging

Consistent logging reader/writer functions for all Node-based Binder modules

Takes a configuration file (the default version in conf/example.main) that specifies how to

  1. connect to a Logstash server for log writing
  2. connect to Elasticsearch/Kibana servers for log reading
  3. stream build logs from a websocket

The example configuration file included in the module has these defaults:

{
  "host": "localhost",
  "testing": true,
  "logstash": {
    "port": 8050,
    "configDir": "~/binder-control/services/logging/logstash/"
  },

  "elasticsearch": {
    "port": 8052,
    "dir": "/data/binder/elasticsearch"
  },

  "kibana": {
    "port": 8053
  },

  "streaming": {
    "port": 2121
  }
}

binder-control can launch Docker containers for Elasticsearch, Logstash and Kibana (with the same default values) through the binder-control start-service logging command. If you'd prefer to use existing logging infrastructure, specify the custom host/port in the config file.

If testing is enabled, the Winston logger will output to both Logstash and stdout (only Logstash otherwise).

install

npm install binder-logging

reader

lib/reader.js contains functions that wrap Elasticsearch queries to make it simpler to search through Binder logs. If you'd prefer to monitor a realtime stream of build logs, the streamLogs function is available (which will connect to Logstash's WebSocket output).

BinderLogReader.getLogs(opts, cb)

Get all historical logs, optionally matching an app name and optionally between before/after times

  • app string - app name to filter on
  • before string - ISO8601 GMT timestamp
  • after string - ISO8601 GMT timestamp
  • cb function - callback(err, msgs)
BinderLogReader.streamLogs(opts)

Stream logs for a given app (mandatory option), optionally since an after timestamp. Returns a through stream

  • app string - app name to filter on
  • after string - ISO8601 GMT timestamp

usage

var getReader = require('binder-logging/lib/reader')
var reader = getReader({ host: '<custom logging host>' })

writer

lib/writer.js exposes a getInstance function that will return a Winston logger given a logger name. This logger exposes the standard logging api (logger.info, logger.error, ...).

getInstance(name)

Returns a Winston logger that's connected to the Binder logging stack

  • name string - logger name (one logger will be created per name, per process)

usage

var getLogger = require('binder-logging/lib/writer')
var logger = getLogger('<logger name>')
logger.info('this is an info message')