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

@log4js-node/rabbitmq

v2.0.0

Published

RabbitMQ Appender for log4js-node

Downloads

132

Readme

RabbitMQ Appender for Log4JS

Push log events to a Rabbitmq MQ. Require log4js-node 2.x or later.

npm install @log4js-node/rabbitmq

If you want to be sure that all messages have been sent before your programme exits, remember to call log4js.shutdown(<callback function>).

Configuration

  • type - @log4js-ndoe/rabbitmq
  • host - string (optional, defaults to 127.0.0.1) - the location of the rabbitmq server
  • port - integer (optional, defaults to 5672) - the port the rabbitmq server is listening on
  • username - string (optional, defaults to guest) - username to use when authenticating connection to rabbitmq
  • password - string (optional, defaults to guest) - password to use when authenticating connection to rabbitmq
  • routing_key - string (optional, defaults to logstash) - rabbitmq message's routing_key
  • durable - string (optional, defaults to false) - will that RabbitMQ lose our queue.
  • exchange - string (optional, defaults to log)- rabbitmq send message's exchange
  • mq_type - string (optional, defaults to direct) - rabbitmq message's mq_type
  • vhost - string (optional, defaults to /) - vhost to use
  • layout - object (optional, defaults to messagePassThroughLayout) - the layout to use for log events (see layouts).
  • shutdownTimeout - integer (optional, defaults to 10000) - maximum time in milliseconds to wait for messages to be sent during log4js shutdown.

The appender will use the RabbitMQ Routing model command to send the log event messages to the channel.

Example

log4js.configure({
  appenders: {
    mq: {
      type: '@log4js-node/rabbitmq',
      host: '127.0.0.1',
      port: 5672,
      username: 'guest',
      password: 'guest',
      routing_key: 'logstash',
      exchange: 'exchange_logs',
      mq_type: 'direct',
      durable: true
    }
  },
  categories: { default: { appenders: ['mq'], level: 'info' } }
});

This configuration will push log messages to the rabbitmq on 127.0.0.1:5672.