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

sbis3-cloud-logger

v0.3.3

Published

Simple logger for SBIS3 Cloud

Downloads

3

Readme

SBIS3 Cloud Logger

Install

npm install sbis3-cloud-logger --save

Use

Module exports a singleton object (only one instance per working process).


var logger = require('sbis3-cloud-logger');

Before sending logs, it must be configured using init() method.

Pass options object to init() to set logger options.


// If both url and cloud is set - priority to cloud
// You MUST specify one of them
logger.init({
    url: 'https://some.host.tld/path/to/backend', // Full logging backend URL.
    cloud: 'online.sbis.ru', // Cloud hostname.
    logThreshold: 500, // how many log records to keep before sending. Default: 100
    queueCheckTime: 5000, // how often to check log buffer. Default: 1000
    appName: 'My Awesome Service', // Application name (appears in log). Default: 'Node'
    sendTimeout: 1000, // If sending is taking this more time, abort it
    appPort: 5555 // Application port (appears in log). Default: 0
});

After first call to init() is made, all further call will be completely ignored.

If cloud parameter is not set while doing init(), exception is thrown.

When done with initialization, use log() method.


logger.log('Bam! Exception!');
logger.log('Loading resources...', 'INFO');
logger.log('Watch out! Memory is almost full!', 'WARNING');

Instead of passing a text message as a first parameter, one can pass object with fields:

  • msg
  • method
  • extip
  • intip
logger.log({
    msg: 'Log message',
    method: 'Object.Method'
});

If init() is not done, all calls to log() is useless and completely ignored.

If you need to forcibly flush logs, use flush() method (since 0.2.0 it flushes logs immediately, not on a next timer tick as of 0.1.0).

To terminate logger (this will prevent further logs transmission) use end() method.

Both methods accepts optional callback which will fire when logs are flushed or error occurs during sending logs.

Hacks

If DISABLE_CLOUD_LOG environment variable is set, logger is doing nothing. All calls to log() are ignored.