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

heroku-events

v0.5.1

Published

This module will mine heroku dyno related events out of a syslog file.

Downloads

5

Readme

heroku-events

This module will mined heroku dyno related events out of a syslog file.

Get Started

To get started with this module you need to enable log sink on your heroku instance, this will send all the logs from your application to a syslog server, which will write this to a file.

To read the a syslog file and create a model representing the state of your application, while also consuming service related events.

var fs = require('fs')
var LogParser = require('heroku-events')

// model for dynos hosts
var model = {}

var logParser = new LogParser(model)

logParser
    .on('newservice', function(service){
        console.log('newservice', service)
    })
    .on('statechangeservice', function(service){
        console.log('statechangeservice', service)
    })

var st = fs.createReadStream('/var/log/heroku.log')
st.pipe(logParser)

Future Work

Need to:

  • rewrite the two core parts to simplify and clean up how the parsing and events work.
  • come up with better names and structure for the change events.