As per https://github.com/balderdashy/sails/issues/811, sailsjs still seems to bear legacy bug from Winston that the logging levels INFO and DEBUG are a different way round to the way you might expect. Some examples that sails differs from:
sysloglog4jloggingwinstonjs (which sails uses for logging :thinking:)I couldn't find any similar examples to sails.
Sails levels are at: https://sailsjs.com/documentation/concepts/logging#?log-levels
As SailsJS is software we use with logging, this difference is highly confusing and has led to a number of misconfigurations of both environments and individual log messages.
@alxndrsn Thanks for posting! We'll take a look as soon as possible.
In the mean time, there are a few ways you can help speed things along:
Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.
For help with questions about Sails, click here.
N.B. this can be "fixed" by adding the following to config/log.js:
logLevels: {
silly: 0,
verbose: 1,
blank: 2,
debug: 2,
info: 3,
warn: 4,
error: 5,
crit: 6,
silent: 7,
},
Most helpful comment
N.B. this can be "fixed" by adding the following to
config/log.js: