4.8.3 • Public • Published

npm GitHub npm GitHub contributors GitHub last commit
node GitHub issues Snyk Vulnerabilities for GitHub Repo David


AwesomeLog is a Log System for enterprise nodejs applications. It provides a basic out of the box logging solution that is ready to go with zero configuration but also gives you a highly configurable logging solution with the power to do your logging right.

Why Another Log Solution?

AwesomeLog is similar to Winston, Log, pino, Log4js, etc. and those are all good products. AwesomeLog just provides a different method of Logging; one we think is cleaner and more stable. If you want to use Winston/Log/pino/Log4js/whatever, that's perfectly fine by us. But if you want to try something a little cleaner, with a bit more features, consider AwesomeLog.


AwesomeLog provides...

  • Ready to go with zero initial configuration;
  • Configure and Start once, Use Everywhere;
  • Support for clean nested AwesomeLog usage;
  • Extremely flexible;
  • Customizable Log Levels;
  • Configurable log entry field contents;
  • Built-In Formatters: Default, JSON, JS, or CSV;
  • Or add your own log formatters;
  • Console and File writers;
  • or add your own custom log writer;
  • Colorized Console Logging;
  • Log History;
  • Pause/Resume;
  • SubProcess Logging;



Couldn't be easier.

npm install --save @awesomeeng/awesome-log


It is best if you configure AwesomeLog at the top of your application. We recommened you do this immediately near the top of your main node entry point.

Setup has three steps:

1). Require AwesomeLog...

const Log = require("@awesomeeng/awesome-log");

2). Configure AwesomeLog...

// for out of the box, zero configuration

// or for more control
	// configuration options go here

3). Start AwesomeLog...


That's it. AwesomeLog is running and you can now use in any part of your application:


To use AwesomeLog once it is configured and started is simple:

1). You need to require AwesomeLog in any file/class that would reference it.

const Log = require("@awesomeeng/awesome-log");

2). Then you just log stuff out.



You'll notice that Log calls take one or more arguments:

  • The first argument is the log message you want to display.
  • All of the remaining arguments are extra details. Depending on the formatter you are using, these may displayed differently. For example, if you use the default formatter, AwesomeLog will attempt to display printable versions of the remaining arguments; Errors in particular are formatted for easier reading.

Log Levels

AwesomeLog starts with five basic Log Levels: ACCESS, ERROR, WARN, INFO, DEBUG by default). Each of these associated methods on the Log instance to allow you to easily use them. So for the default levels you get


If you customize the log levels, AwesomeLog will remove the default log level methods (Log.warn() etc) and replace them with methods that have your log levels names:

	levels: "silly,goofy,funny,bad"

You may have as many Log Levels as you desire, but each must have a unique name. Also, there are a handful of reserved words (anything that is already in the AwesomeLog class) and you cannot use them. These include: AbstractLogWriter, AbstractLogFormatter, initialized, running, config, history, historySizeLimit, levels, levelNames, definedWriters, definedFormatters, defineWriter, defineFormatter, init, start, stop, pause, resume, clearHistory, getLevel, log, captureSubProcess, releaseSubProcess.

In addition to the log level methods, you also use the Log.log() method which takes the level as the first argument, so you can programmatically set the level if needed.


Log Writers

A Log Writer is the channel by which a log message is written to some output device. Writers are used to send the message to the console, the file system, a database, wherever you need your logs to end up.

AwesomeLog ships with three built-in Log Writers:

  • Console: Used to output log messages to the STDOUT console. Has the option to colorize output for ANSI compatible terminals.

  • File: Used to output log message to a given file. Has the capability to specify custom file names including date patterns, and support file rotation and cleanup.

  • Null: Used to output log messages to /dev/null and make them disappear forever.

By default AwesomeLog is configured to use the Console writer only. You can change the writers during your Log.init() call if you so desire. Here's an example:

	writers: [{
		name: "MyConsoleWriter",
		type: "console",
		formatter: "default",
		options: {
			colorize: true
		name: "MyFileWriter",
		type: "file",
		formatter: "json",
		options: {
			housekeeping: "2 hours",
			filename: "logs/MyLogs.{YYYYMMDD}.log"

This example enables two writers, a console writer and a file writer.

You can read more about Configuration, Console Writer, or File Writer, or how to write your own Custom Log Writer in the respective documentation.

Each LogWriter is run in its own isolated process and log messages are passed to it. This allows AwesomeLog to execute much faster.

Log Formatters

A Log Formatter takes the log message details (as well as a number of other system information details) and formats that into a single string message. Each Log Writer (see above) can have it's own Log Formatter. If you do not provide a formatter, default is used.

AwesomeLog ships with four built-in Log Formatters:

  • Default: The default formatter outputs log messages in AwesomeLog's own custom format. This includes the timestamp, the process id, the log level, the log system name, the log message, and any additional arguments.

    2018-09-10T15:46:27.714Z : #1234 : INFO       : AwesomeLog.js    : Log initialized.
    2018-09-10T15:46:27.716Z : #1234 : INFO       : AwesomeLog.js    : Log started.
  • JSON: The JSON formatter writes the entire log message out as a json string. You'll notice that there is a lot more detail in this example when compared with the one for default from above. Formatters often reduce the amount of log information.

    {"hostname":"blah.awesomeeng.com","domain":"awesomeeng.com","servername":"blah","pid":1234,"ppid":5678,"main":"/code/project","arch":"x64","platform":"linux","bits":64,"cpus":8,"argv":"","execPath":"node","startingDirectory":"/code/project","homedir":"/home/blah","username":"blah","version":"v10.9.0","level":"INFO","system":"AwesomeLog.js","message":"Log initialized.","args":[],"timestamp":1536594573580}
    {"hostname":"blah.awesomeeng.com","domain":"awesomeeng.com","servername":"blah","pid":1234,"ppid":5678,"main":"/code/project","arch":"x64","platform":"linux","bits":64,"cpus":8,"argv":"","execPath":"node","startingDirectory":"/code/project","homedir":"/home/blah","username":"blah","version":"v10.9.0","level":"INFO","system":"AwesomeLog.js","message":"Log started.","args":[],"timestamp":1536594573582}
  • CSV: The CSV formatter outputs the log information in a CSV format friendly to spreadsheets. The CSV format is timestamp(unix epoch),level,pid,system name,message,arg0,arg1,...arg9999.

    1536594995710,"INFO",19848,"AwesomeLog.js","Log initialized."
    1536594995712,"INFO",19848,"AwesomeLog.js","Log started."
  • JS: The JS formatter outputs the log information as a JavaScript Object. It is more suited to programatic uses then to human readable usage.

    [object Object]
    [object Object]

You can read more about how to write your own Custom Log Formatter in the documentation.


AwesomeLog supplies a variety of field options. During configuration you can specify which fields you want to be in each log entry, although what gets output is also determined by the log formatter you choose. For example, you can specify the hostname field, but the Default formatter doesnt use it. Some formatters do output the entire log entry structure though like the CSV Formatter, the JSON formatter, or the JS Object formatter.

It is worth noting that some fields are more expensive than others, performance wise. In particular, the system field if very expensive from a performance point of view. If performance is a consideration for you, please consider leaving this field out.

Fields are configured thus:

	fields: "timestamp,pid,system,text,args"

The fields configuration property is a comma delimited string of each field name. Order is irrelevant as the formatter you choose will dictate its own ordering.

The default fields are timestamp,pid,system,text,args. If your NODE_ENV environment variable is set to prod or production the default fields will omit system to encourage better performance on production environments.

The following fields are available:

  • timestamp: The current time, in UTC.
  • level: The log level for this particular log entry.
  • text: The text message for this particular log entry.
  • args: Any extra arguments passed to the log call.
  • system: The javascript file in which this log call was made. Please note that including this field is very expensive from a performance standpoint, and it should only be used in development systems.
  • system:: Like system, but move X number of places down the stack to find the system name. This is useful if you have wrapped AwesomeLog in a service of some sort and system always reports that wrapper name. X is an integer. By default X is 1 and a value of 0 is not allowed. Like system above this comes with significant performance costs and should only be used in development.
  • hostname: The hostname of the machine the log event occured on. Good for integrated log systems.
  • domain: The domain name portion of the hostname, that is the last two segments of the hostname.
  • servername: The computer name for the machine the log event occured on. This is the first segment of the hostname.
  • pid: The process id for this log message. In subprocess systems this can be a valuable debugging tool.
  • ppid: The parent process id.
  • main: The path to the executed node executable.
  • execpath: The path to the executed node executable.
  • argv: The initial arguments passed to the executed node executable.
  • arch: The architecture value for the current OS.
  • platform: The platform value for the current OS.
  • bits: The bits value for the current OS.
  • cpus: The number of physical CPUs on the current machine.
  • startingdir: The starting directory of the node application.
  • homedir: The user's home directory.
  • username: The user's username.
  • version: The version of node.


AwesomeLog is configured by default to perform in manner best suited to development. For production systems, a slioghtly more nuanced configuration will perform better, but at a reduction in development information. When run with this performance configuration AwesomeLog will perform slightly better than most other nodejs logging systems like Winston, Bunyan, Bole, Debug, etc. and performs about the same as pino.

Recommended production configuration

	fields: "timestamp,level,pid,text,args",
	separate: true,
	buffering: true,
	history: false

With regards to the fields configuration property: most fields are fine, however, the system field does add a significant performance cost and should only be used in development environments.



AwesomeLog ships with a set of examples for your reference.

The Awesome Engineering Company

AwesomeLog is written and maintained by The Awesome Engineering Company. We belive in building clean, configurable, creative software for engineers and architects and customers.

To learn more about The Awesome Engineering Company and our suite of products, visit us on the web at https://awesomeeng.com.

Support and Help

This product is maintained and supported by The Awesome Engineering Company. For support please file an issue or contact us via our Webiste at https://awesomeeng.com. We will do our best to respond to you in a timely fashion.


AwesomeLog is released under the MIT License. Please read the LICENSE file for details.

Package Sidebar


npm i @awesomeeng/awesome-log

Weekly Downloads






Unpacked Size

237 kB

Total Files


Last publish


  • arei