Fetching contributors…
Cannot retrieve contributors at this time
43 lines (29 sloc) 2.86 KB


Sails comes with a simple, built-in logger called captains-log. Its usage is purposely very similar to Node's console.log, but with a handful of extra features; namely support for multiple log levels with colorized, prefixed console output. The logger serves two purposes:

  • it emits warnings, errors, and other console output from inside the Sails framework
  • it can be used to emit custom events/messages from within your application code


Sails' log configuration is determined by sails.config.log, which is conventionally set by a generated configuration file (config/log.js) in new Sails projects out of the box.

Usage'I am an info-level message.');
sails.log('I am a debug-level message');
sails.log.warn('I am a warn-level message');

Log levels

Using the built-in logger, Sails will write output (to stdout/stderr) for log function calls that are at or above the priority of the currently-configured log level. This log level is normalized and also applied to generated output from Grunt,, Waterline, Express, and other dependencies. The hierarchy of log levels and their relative priorities is summarized by the chart below:

Priority Level Log fns that produce visible output
0 silent N/A
1 error .error()
2 warn .warn(), .error()
3 debug .debug(), .warn(), .error()
4 info .info(), .debug(), .warn(), .error()
5 verbose .verbose(), .info(), .debug(), .warn(), .error()
6 silly .silly(), .verbose(), .info(), .debug(), .warn(), .error()


  • The default log level is info. When your app's log level is set to "info", Sails logs limited information about the server/app's status.
  • When running automated tests for your app, it is often helpful to set the log level to error.
  • When the log level is set to verbose, Sails logs Grunt output, as well as much more detailed information on the routes, models, hooks, etc. that were loaded.
  • When the log level is set to silly, Sails outputs everything from verbose as well as internal information on which routes are being bound and other detailed framework lifecycle information, diagnostics, and implementation details.