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

@hkube/logger

v2.0.2

Published

best logger ever ;-)

Downloads

385

Readme

Logger

the best js logger ever :)

The following options available

  • running logs with elastic fluentd conosle and view in kibana
  • costomize your log level and colors by sending it from the logger constructor the following availble by default debug,info,warning,error,critical
         const config = {
            levels: {
                silly: 0,
                debug: 1,
                info: 2,
                warning: 3,
                error: 4,
                critical: 5
            },
            colors: {
                silly: 'white',
                debug: 'grey',
                info: 'white',
                warning: 'yellow',
                error: 'red',
                critical: 'red'
            }
        };
  • creating multiple log that differnts from each other
  • lazy loading your log from each module Logger.GetLogFromContanier(ServiceName)
  • controling log trace level and update it during run using updateTraceLevel(levelNumber)
  • an abiltiy to set component name and other metaData log.info('hi info test',{component: 'test-Component'});
  • costomize your log colors with colors api for example log.info('hi info test'.green); or log.info(('hi info test')[green]);
  • builtin metadata addition such as printing call stack trace for error and critical
  • additions with extra details for logs during run by setting extraDetails flag to true will print this as extrad details {{ function: null file: /home/matyz/dev/vod/core/logger/test/test.js lineNumber: 160 }}
  • built in template that includes time log level and component name September 1st 2016, 12:26:52 pm -> info: ( test-Component ) hi info test

running

in order to run you can clone the repo or using npm install logger

configuration


transport : {
    console: true,
    file: true,
    redis : true
    logstash: true,
},
console: {
    json: true,
	colors: true
},
file: {
    json: true,
	colors: true
    level: 'info',
    silent: false,
    eol: null,
    filename: 'data/info.log',
    maxsize: 10000,
    maxFiles: 1000,
    tailable: true,
    maxRetries: 2,
    zippedArchive: false,
    options: { flags: 'a' },
},
redis: {
    json: true,
	colors: true
    host: 'localhost',
    port: 6379,
    sentinel: true,
    verbosityLevelByRedis: true,
    level: 'error'
},
logstash : {
    json: true,
	colors: true
    logstashURL: '127.0.0.1',
    logstashPort: 28777
},
options: {
    extraDetails: false
}

usage example:

init

const Logger = require('logger');
const log = new Logger('test',relativeConfig);

get created logger

  • use this if know the log container name
const log = Logger.GetLogFromContainer(ServiceName);
  • don't need to send container name if set this logger as default with isDefault:true
const log = Logger.GetLogFromContainer();

log printing

  log.info('running application in ' + conf.env() + ' environment', {component: componentName.MAIN});    
  log.error('Error response, status=' + res.status + ', message=' + res.error.message, {component: componentName.REST_API});

redis config

`hkube:logs:consoleVerbosity` key set the console log verbosity default `info`
`hkube:logs:clientVerbosity` key set the ui log verbosity default `error`

ENJOY :)