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

egg-logger-remote

v1.1.0

Published

Logger transport for remote server

Downloads

9

Readme

egg-logger-remote

NPM version build status Test coverage David deps Known Vulnerabilities npm download

Install

$ npm i egg-logger-remote --save

Usage

// {app_root}/config/plugin.js
exports.loggerRemote = {
  enable: true,
  package: 'egg-logger-remote',
};

Configuration

// {app_root}/config/config.default.js
exports.loggerRemote = {
};

see config/config.default.js for more detail.

Disable Logger

You and disable logger with disable config.

exports.loggerRemote = {
  disable: [
    // won't upload this logger
    'myLogger',
  ],
}

Transform and Filter

You can transform the log data before upload.

exports.loggerRemote = {
  transform(log, args) {
    return log;
  },
}

If you want to ignore some log, you can return false when transform.

exports.loggerRemote = {
  transform(log) {
    if (some condition) return false;
    return log;
  },
}

There is two arguments that transform have.

  1. One is log object, it contains the default property, which is ip, hostname, env, appName, loggerName, loggerFileName, level. The last one is content that is the log string formated from the arguments when you call log method.
  2. The other is original arguments when you call log method, it will not format to content.

Data Structure

The data structure uploaded in below, you can create index in aliyun console as your wish.

  • level: logger level
  • content: the infomation that you logged
  • ip: the host ip
  • hostname: the host name
  • env: the egg environment
  • appName: the package name
  • loggerName: the logger name defined by Egg
  • loggerFileName: the logger file path

Logger Level

The default logger in Egg contains two level: level and consoleLevel, If you want set level for sls, you can use slsLevel.

// config/config.default.js
module.exports = {
  loggerRemote: {
    // for all logs
    remoteLevel: 'DEBUG',
  },
};

If slsLevel is not specified, it will use level instead.

Example

Questions & Suggestions

Please open an issue here.

License

MIT