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

@gpuprog/log

v1.2.8

Published

Logging for microservices

Downloads

15

Readme

Purpose

This log module can be used in microservices on JS and Python to write common (combined, or single) log file and also to notify administrator about errors. The module provides similar format for different microservices and single configuration point (environment variables) that can be useful on server with SaaS b ased on different microservices.

How to use

Configuration in code

In code it's recommended to set module name with a call: log.set_module_name(name).

Session identificator (sid)

Sid is any (optional) string that can identify the session.

Log format

Any message has common format like: [module][datetime] level [sid] message Where:

  • module - configurable name
  • datetime - date and time of log call by format YYYY-MM-DD hh:mm:ss.ms
  • level - level of message, INFO, WARN, ERROR (and internal *CRITICAL* for logger internal errors)
  • sid - Session identificator (can be undefined/None)

Logging (by levels)

To log any message use following functions by appropriate levels (sid is optional argument):

  • log.info(message, sid)
  • log.warn(message, sid)
  • log.error(message, sid)

Levels "info" and "warn" logged into stdout and log file only but level "error" also generates e-mail and Telegram message.

External configuration

The logger configured with environment variables. Additionally to always enabled stdout/stderr you can enable up to three channels for logging by following variables:

  • Log all levels of messages to file (can be used from different processes in parallel)
    • LOG_FILENAME=<Filename for .log in HOME folder>
  • Send e-mail per each error level message (with call stack)
    • SENDER_GMAIL=<Your Gmail proxy account to send e-mails>
    • SENDER_GMAIL_PASSWORD=<Your Gmail proxy account app password> - see how to configure Gmail app password
    • ADMIN_EMAIL=<Admin e-mail to get critical error messages>
  • Send Telegram notification per each error-level message (with call stack) - see how to get Telegram the Bot Token and the Chat ID
    • TELEGRAM_BOT_TOKEN=<Your Telegram bot token>
    • TELEGRAM_CHAT_ID=<The chat ID to send messages>

Integration

Recommended way for integration is to use it as git submodule - to update it for your requirements.

import log

const log = require('@gpuprog/log/log')

Development

cd log