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

loganalyzer

v0.3.0

Published

A simple log analyzer supporting multiple filters and UI.

Downloads

7

Readme

loganalyzer

This is a general log analysis tool that helps anyone to take an easier approach at filtering the critical lines they care about, do some processing for the matching fields, and output critical results for potential automation pipeline.

Usage:

The core of the log analysis tool revolves around a configuration file that users can customize.

{
  "debug": "Set to true for debug output or leave the option out for non-debug",
  "jsonOutput": "true or leave the option out for normal output",
  "filters": [{
    "pattern": "Regular expression matching each line, with brackets capturing interested fields",
    "desc": "Description of this particular filter" 
    "fields": [{
      "name": "Name of first matched field",
      "color": "Color of your matched field in the output"
    }, {
      "name": "Name of second matched field",
      "color": "Color of your matched field in the output"
    },
    ...
    ]
  }, {
    "pattern": "Second pattern to recognize",
    "desc": "Second filter",
    ...
  }]
}

Please see samples/configs for actual examples

When running on a single log file:

node main.js {config_file_path} {log_file_path}

When running on a pipe stream, for example, a logcat from the Android Debug Bride (ADB logcat):

{stream input. i.e. adb logcat} | node main.js {config_file_path}