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

toto-logger

v5.0.0

Published

This npm library standardizes the way that toto microservices will log information.

Downloads

18

Readme

Toto Logger

This npm library standardizes the way that toto microservices will log information.

Logs in toto have the following structure:

> [correlationID] - [apiName] - [logType] - [logLevel] - Message

Where:

  • correlationID should be always present for apis and reactive microservices and is the identifier that can be used to track the flow of data through sync and async calls
  • logType is the type of log. The following log types are accepted:
    • api-in - reserved - to be used only when receiving an API call. This log type must be used only once and only at the moment the API call is received: it shouldn't be used for subsequent log entries. It is only used to record the fact that an API call has been received!
    • api-out - reserved - to be used only when making an outbound API call.
    • event-in - reserved - to be used only when receiving an Event. Same logic applies as for the api-* log type.
    • event-out - reserved - to be used only when publishing an Event. Same logic applies as for the api-* log type.
    • compute - can be used for any log happening during the computation that results from the receiving an event or an api call.
  • logLevel is the level of the log. Should only be:
    • debug - only used for debugging purposes
    • info - used for standard info logging
    • warn - used to log warnings
    • error - used to log errors

How to use it

Instantiate it:

const Logger = require('toto-logger');
let logger = new Logger("apiname");

Log, based on the type of log

logger.apiIn(correlationId, method, path);
logger.apiOut(correlationId, microservice, method, path);
logger.eventIn(correlationId, topic);
logger.eventOut(correlationId, topic);
logger.compute(correlationId, message, logLevel);