Node logging has problems. The average node project has libraries logging to the
console, internal logs using winston or
bunyan, and frameworks logging in their own format.
The end result is usually this:
192.442.345.32 - - [Mon, 09 Oct 2017 23:23:37 GMT] "GET / HTTP/1.1" 304 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36"
Log message from console.warn
{"level":"debug","message":"Log message from winston"}
Timber solves this by normalizing and augmenting your logs with structured data, regardless of the source. This not only normalizes your logs, but captures additional useful metadata:
GET / HTTP/1.1 @metadata {"dt": "2017-10-08T23:23:37.234Z", "level": "info", "context": {"http": {"remote_addr": "192.442.345.32"}}, "event": {"http_request": {"method": "GET", "path": "/", "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36"}}}
Log message from console.warn @metadata {"dt": "2017-10-08T23:23:37.234Z", "level": "warn"}
Log message from winston @metadata {"dt": "2017-10-08T23:23:37.234Z", "level": "debug"}
Ah! Consistent, easy to use logs. To get started:
console, winston, and bunyan.Signup at timber.io and follow the in-app instructions.
For those interested in manual instructions, see the timber.io installation docs.
No special API, Timber works directly with your logger of choice:
// console
console.log("My log message")
console.info("My log message")
console.warn("My log message")
console.error("My log message")
// winston
winston.info("My log message")
winston.warn("My log message")
// ...
// bunyan
logger.info("My log message")
logger.warn("My log message")
// ...
Log structured data without sacrificing readability:
// console
console.warn("Payment rejected", {
event: {
payment_rejected: { customer_id: "abcd1234", amount: 100, reason: "Card expired" }
}
});
// winston
winston.warn("Payment rejected", {
event: {
payment_rejected: { customer_id: "abcd1234", amount: 100, reason: "Card expired" }
}
});
// bunyan
logger.warn({
event: {
payment_rejected: { customer_id: "abcd1234", amount: 100, reason: "Card expired" }
}
}, "Payment rejected");
Context for node is coming soon! Because node does not have a concept of local storage, we're working to implement continuation local storage. This will enable shared join data across your logs, allowing you to relate them.
Star / watch this repo to be notified when this goes live!
If you're using express, you can use the timber middleware to automatically log all http request/response events
const express = require('express')
const timber = require('timber')
// first we create a writeable stream that your logs will get sent to
const transport = new timber.transports.HTTPS('your-timber-api-key');
// attach the stream to stdout
timber.install(transport);
// create our express app
const app = express()
// attach the timber middleware
app.use(timber.middlewares.express())
app.get('/', function (req, res) {
res.send('hello, world!')
})
// Output:
// => Started GET "/" @metadata {"level": "error", "context": {...}}
// => Outgoing HTTP response 200 in 2ms @metadata {"level": "error", "context": {...}}
The express middleware accepts a single argument for configuration options. To learn more about the available options, visit the express integration docs
If you're using winston, you can use the winston transport to send all of winston's logs to timber.io
const winston = require('winston')
const timber = require('timber')
const transport = new timber.transports.HTTPS('your-api-key')
timber.install(transport)
winston.remove(winston.transports.Console)
winston.add(winston.transports.Console, {
formatter: timber.formatters.Winston
})
winston.log('info', 'Sample log message')
// Output:
// => Sample log message @metadata {"level": "info", ... }
When you pass a metadata object to winston, timber will automatically augment your log line with it:
winston.log('info', 'Log message with metadata', { user: 'username' })
// Output:
// => Log message with metadata @metadata {"level": "info", meta: { user: 'username' }, ... }
You can augment your log with a custom event by providing an event key at the root of your metadata object:
winston.log('info', 'Log message with event', { event: custom_event_name: { ... } })
// Output:
// => Log message with event @metadata {"level": "info", event: { custom_event_name: { ... } }, ... }
Adding custom context is just as easily done by adding the context key to the root of your metadata object:
winston.log('info', 'Log message with event', { context: { ... } })
// Output:
// => Log message with event @metadata {"level": "info", context: { ... }, ... }
If you're using the timber express middleware, you'll most likely want to configure it to use winston as the logger. This can be done by setting the logger config attribute to winston:
timber.config.logger = winston
If you're using bunyan, you can use the bunyan transport to send all of bunyan's logs to timber.io
const bunyan = require('bunyan')
const timber = require('timber')
const winston = require('winston')
const timber = require('timber')
const transport = new timber.transports.HTTPS('your-api-key')
timber.install(transport)
const log = bunyan.createLogger({ name: 'Timber Logger' })
log.info('Sample log message')
// Output:
// => Sample log message @metadata {"level": "info", ... }
If you want to augment your log with custom metadata, simply add an object as the first argument:
log.info({ user: 'username' }, 'Log message with metadata')
// Output:
// => Log message with metadata @metadata {"level": "info", meta: { user: 'username' }}, ... }
You can augment your log with a custom event by providing an event key at the root of your metadata object:
log.info({ event: { custom_event_name: { ... } } }, 'Log message with event')
// Output:
// => Log message with event @metadata {"level": "info", event: { custom_event_name: { ... } }, ... }
Adding custom context is just as easily done by adding the context key to the root of your metadata object:
log.info({ context: { ... } }, 'Log message with event')
// Output:
// => Log message with event @metadata {"level": "info", context: { ... }, ... }
If you're using the timber express middleware, you'll most likely want to configure it to use bunyan as the logger. This can be done by setting the logger config attribute to the bunyan logger you created:
timber.config.logger = log
By default, Timber makes attaching to stdout and stderr very easy through the convenient timber.install(transport) function.
However, it's possible to attach the transport to any writeable stream
using the timber.attach() function!
const transport = timber.transports.HTTPS('timber-api-key')
// This is what the install() command is doing:
timber.attach([transport], process.stdout)
timber.attach([transport], process.stderr)
// => This sends all logs from stdout directly to Timber
// You can attach multiple unique transport streams to each stream:
const file_transport = fs.createWriteStream("./output.log", {flags: "a"})
timber.attach([transport, file_transport], process.stdout)
// => This sends all logs from stdout to Timber, stdout, and a custom log file
Timber integrates with popular frameworks and libraries to capture context and metadata you couldn't otherwise. This automatically augments logs produced by these libraries, making them easier to search and use. Below is a list of libraries we support:
...more coming soon! Make a request by opening an issue
Logging features designed to help developers get more done:
FAQs
Timber.io node client.
The npm package timber receives a total of 47 weekly downloads. As such, timber popularity was classified as not popular.
We found that timber demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.