Warning
n-logger has been deprecated as of 2023-04-17. It will reach end-of-life on 2023-10-20 at which point no further security patches will be applied. The library will continue to work in currently-supported versions of Node.js but it should not be used in new projects. The recommended replacement is Reliability Kit logger.
This package provides a Winston wrapper which sends server-side logs to Splunk's HTTP Event Collector (HEC).
Please note that this package is not only used by the Customer Products team. Please be mindful of this as any changes may impact other teams, such as Internal Products, differently.
This package is compatible with the Node version defined by engines.node
in package.json
(run command nvm use
to switch your local Node version to the one specified in .nvmrc
) and is distributed on npm.
npm install --save @financial-times/n-logger
After installing the package you will need to configure your production application with the SPLUNK_HEC_TOKEN
environment variable. If you are working on a next-
application this will be specified in the shared secrets folder in Vault.
import logger from '@financial-times/n-logger';
logger.log('info', 'Saying hello');
logger.info('Saying hello');
logger.warn('Everything’s mostly cool');
logger.error('Uh-oh', { field: 'some value' });
logger.info({ event: 'UPDATE_NOTIFICATION', data: data });
const error = new Error('Whoops!');
logger.error('Uh-oh', error, { extra_field: 'boo' });
If using CommonJS modules:
const logger = require('@financial-times/n-logger').default;
The default loggers are configured based on the presence of several environment variables. A Console
logger is always registered and a SplunkHEC
logger is registered depending on which variables are set:
-
MIGRATE_TO_HEROKU_LOG_DRAINS
: Whether the app should rely on Heroku log drains in production. If this variable is set to an unempty string then the app will not log directly to Splunk. Instead it will log JSON strings to the console which should be picked up by Heroku and forwarded on to Splunk. Do not set this environment variable before configuring a Heroku log drain in your application. -
SPLUNK_HEC_TOKEN
: The Splunk token to use when manually sending logs to Splunk. If this is set to an unempty string then a SplunkHEC logger will be configured. -
SPLUNK_LOG_LEVEL
: The log levels to send to Splunk, used by both Heroku log drains and the SplunkHEC logger. Defaults towarn
. -
CONSOLE_LOG_LEVEL
: The log levels to send to the console. Defaults tosilly
. This environment variable is ignored in favour ofSPLUNK_LOG_LEVEL
whenMIGRATE_TO_HEROKU_LOG_DRAINS
is in use. -
CONSOLE_LOG_UNCOLORIZED
: Set totrue
to disable log coloring. By default console logs are colorized. This environment variable is ignored whenMIGRATE_TO_HEROKU_LOG_DRAINS
is in use as JSON logs are not colorized.
If you are making a change to n-logger
it is worth testing it locally to check it is sending logs successfully before merging.
- Create a test.js file in the root of your local n-logger.
- Add the following to this file:
const logger = require('./dist/main').default;
logger.warn('Testing Testing Testing');
logger.warn({ event: 'HELLO_WORLD', message: 'Testing 1 2 3', count: 5 }, {fizz: 'buzz'});
-
In the terminal
export NODE_ENV=production
,export SYSTEM_CODE=next-foo-bar
andexport SPLUNK_HEC_TOKEN={token}
(find this token in thenext/shared
folder in Vault). -
Run
node test
in the terminal. -
If everything is working correctly, you should be able to see your test logs in Splunk with the query
index=heroku source="/var/log/apps/heroku/ft-next-foo-bar.log"
.
level
can be silly, debug, verbose, info, warn or errormessage
is optional- any number of meta objects can be supplied, including
Error
objects - IMPORTANT NOTE - do not send errors as properties of other objects, e.g.
{event: 'My_EVENT', error}
. This will result in no details of the error being logged**
Additional metadata
properties to be appended to every subsequent log call.
The Winston object