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

kuzzle-plugin-logger

v3.0.3

Published

Kuzzle plugin that handles logs

Downloads

2,642

Readme

About

Kuzzle Logger Plugin

This plugin is a bridge between Kuzzle and the winston package. It is part of the default plugins provided with Kuzzle.

Currently, three winston transports are supported:

  • stdout (winston Console)
  • file (winston File)
  • syslog (from winston-syslog)

Kuzzle

Kuzzle is a ready-to-use, on-premises and scalable backend that enables you to manage your persistent data and be notified in real-time on whatever happens to it. It also provides you with a flexible and powerful user-management system.

How to create a plugin

Please refer to Kuzzle plugin development documentation for more information on how to build you own plugins.

Get trained by the creators of Kuzzle :zap:

Train yourself and your teams to use Kuzzle to maximize its potential and accelerate the development of your projects.
Our teams will be able to meet your needs in terms of expertise and multi-technology support for IoT, mobile/web, backend/frontend, devops.
:point_right: Get a quote

Compatibility matrix

| Kuzzle Version | Plugin Version | | -------------- | -------------- | | 1.8.x | 2.x.x | | 2.x.x | 3.x.x |

Configuration

Each transport can be added and configured by adding it to the services entry.

The content of this section is almost passed as-is to winston related transport constructor.

The only exception is addDate and dateFormat parameters, which are specific to Kuzzle and allow to specify a custom date format using only plain-text configuration, using moment format.

:warning: Contrary to winston, it is not possible to pass a function to any option.

Sample:

{
  "threads": 2,
  "services": {
    "file": {
      "level": "warn",
      "filename": "kuzzle.log",
      "addDate": true,
      "dateFormat": "dddd, MMMM Do YYYY, h:mm:ss a"
    },
    "stdout": {
      "level": "info",
      "addDate": "true"
    },
    "syslog": {
      "protocol": "unix",
      "path": "/dev/log",
      "facility": "local6"
    }
  }
}

Default configuration

If no configuration is given, this plugin will output logs to the console only, from info level and above.

Transports configuration references

Date formatting

Native winston date related/timestamp configurations are merged during the plugin init for transports that support it.

In other words, timestamp and addDate can be used indifferently for stdout and file transports:

{
  "services": {
    "stdout": {
      "timestamp": true,
      "dateFormat": "YYYY-MM-DD HH-mm-ss"
    }
  }
}