log inbound/outbound HTTP traffic
npm install @workablehr/riviere
The riviere module decorates your Koa middleware chain with inbound/outbound HTTP traffic logs.
Use riviere if you want an easy way to log all the HTTP traffic for your server.riviere works independently of your logging library, if you use any.
---
---
- Log all the HTTP(s) requests that are coming into your server and the corresponding responses.
(inbound_request/outbound_response)
- Log all the HTTP(s) requests that your server sends to any external systems and the corresponding responses.
(outbound_request/inbound_response)
- Log any unhandled errors that are thrown inside a requests's context.
- Format logs in json (fully compatible with Google Stackdriver)
---
The above example logs are generated by executing:
``js`
curl localhost:3000 -H "X-myHeader: myHeaderValue"
Assuming that the following example server is running:
!examples/hello_with_outgoing_traffic.js
---
* Node version >= 8
* Koa version >= 2
---
`npm i --save riviere`
---
Example:
`js
const Koa = require('koa');
const riviere = require('riviere');
const app = new Koa();
app.use(riviere());
app.use(async function(ctx) {
ctx.body = 'Hello World';
});
app.listen(3000);
`
Example with outbound HTTP traffic:
`js
const Koa = require('koa');
const riviere = require('riviere');
const app = new Koa();
app.use(riviere());
app.use(async function(ctx) {
await fetch('https://www.google.com', {
// You can include the x-riviere-id header
// to trace the request's context inside which
// the external request is made
// This is optional but recommended for better tracing:
headers: {
'x-riviere-id': ctx.request.headers['x-riviere-id'] // notice that this is lowercase
}
});
ctx.body = 'Hello World';
});
app.listen(3000);
`
---
The behavior of the riviere middleware can be configured by passing a configuration object,
as argument to the riviere() method call.
You can start using riviere' by just calling app.use(riviere()).riviere
In this case the will use its default configuration.
The default configuration object is the following:
`js`
const configuration = {
context: ctx => {
return {};
},
errors: {
enabled: true,
callback: (err, ctx) => {
throw(err);
}
},
health: [],
inbound: {
enabled: true,
request: {
enabled: true
},
maxBodyValueChars: undefined
},
outbound: {
enabled: true,
request: {
enabled: true
},
maxBodyValueChars: undefined
},
bodyKeys: [],
bodyKeysRegex: undefined,
bodyKeysCallback: (body: any, ctx?: KoaContext) => ({}),
headersRegex: new RegExp('^X-.*', 'i'),
traceHeaderName: 'X-Riviere-Id',
styles: ['simple'],
}
Here is an example of a more advanced configuration:
`js
const configuration = {
bodyKeys: [
'education',
'work_experience'
],
color: true,
context: (ctx) => {
return {
userId: ctx.request.headers['user-id'],
accountId: ctx.request.headers['account-id']
};
},
errors: {
enabled: true,
callback: (ctx, error) => {
ctx.status = error.status || 500;
if (ctx.status < 500) {
ctx.body = {error: error.message};
} else {
ctx.body = {error: 'Internal server error'};
}
}
},
headersRegex: new RegExp('X-.+', 'i'),
health: [
{
path: '/health',
method: 'GET'
}
],
outbound: {
enabled: true
},
traceHeaderName: 'X-Request-Id',
styles: ['simple', 'json']
};
app.use(riviere(configuration));
`
The supported key-value options, for the configuration object are described below.
---
Enable inbound HTTP traffic logging. Defaults to true.
Enable inbound_request HTTP traffic logging. Defaults to true.
Log full path, including host on inbound requests. Defaults to false.
This option can be used to truncate values JSON body of the inbound POST requests to a specified length. Defaults to undefined.POST
To use this option, the request's body should be a valid JSON.
Example:
`js`
{
inbound: {
maxBodyValueChars: 1024
}
}
This option can be used to log specific values from the JSON body of the inbound POST, PUT & PATCH requests.[]
Defaults to empty Array .JSON
To use this option, the request's body should be a valid .Koa
Most often this mean that you should register the bodyParser middlewareriviere
(https://www.npmjs.com/package/body-parser) (or something equivalent),
before registering the middleware.
Example:
`js`
{
bodyKeys: [
'education',
'work_experience'
]
}
This option can be used to log specific values from the JSON body of the inbound POST, PUT & PATCH requests.JSON
Defaults to undefined.
To use this option, the request's body should be a valid .Koa
Most often this mean that you should register the bodyParser middlewareriviere
(https://www.npmjs.com/package/body-parser) (or something equivalent),
before registering the middleware.
This option will override bodyKeys
Example:
`js`
{
bodyKeysRegex: new RegExp('.*');
}
This option can be used to let you choose which fields should be logged on inbound POST, PUT & PATCH requests.JSON
Defaults to undefined.
To use this option, the request's body should be a valid .Koa
Most often this mean that you should register the bodyParser middlewareriviere
(https://www.npmjs.com/package/body-parser) (or something equivalent),
before registering the middleware.
This option will override bodyKeys and bodyKeysRegex
Example:
`js`
{
bodyKeysCallback: (body: any, ctx?: KoaContext) => {
if (!ctx) return body;
return {
...body,
fields: body.fields.filter(f => !f._obfuscated)
}
};
}
Log colored log messages. Defaults to: true
Example:
`js`
{
color: true
}
This option is used to format log messages with specific styles. Defaults to: ['simple']
If multiple options are defined one line is exported for every different style.
Available options are:
- 'simple': Prints method, path, status code and timing followed by ' | ' and a string containing key-value pairs of object properties
- 'extended': Same as simple but also contains key-value pairs of all properties (fully compatible with LogEntries)
- 'json': All object properties as a valid JSON object (fully compatible with Google Stackdriver)
Example:
`js`
{
styles: ['simple', 'json']
}
The context to be included in every inbound_request and outbound_response
log message. Defaults to empty Object: .
Example:
`js`
{
context: (ctx) => {
return {
userId: ctx.request.headers['user-id'],
accountId: ctx.request.headers['account-id']
};
}
}
Enable inbound HTTP traffic logs. Defaults to true.
Control how the server handles any unhandled errors inside a request's context.
The default is to re-throw the unhandled error.
Example:
`js
{
errors: {
callback: (err, ctx) => {
ctx.status = err.status || 500;
if (ctx.status < 500) {
ctx.body = {error: err.message};
} else {
ctx.body = {error: 'Internal server error'};
}
}
}
}
`
Specify a regular expression to match the request headers,
that should be included in every inbound_request log message.new RegExp('^X-.+', 'i')
Defaults to .
All the inbound request's headers starting with "X-" will be logged by default.
Example:
`js`
{
headersRegex: new RegExp('X-.+', 'i')
}
This option can be used to let you modify or change part or the whole value of a header.
This function will be applied to all headers that are passed based on the headersRegex. key
This function takes two argument, the (i.e. the header name) and the value (i.e. the header value) and returns the new value of the header.
This function is very useful in cases where is mandatory to hide or remove sensitive data that is part of the header value.
Defaults to undefined. In case of undefined then the header value will remain as is.
Example:
In this example we hide some sensitive id_token value.
`js`
{
headerValueCallback: (key, value) {
const regex = /id_token=[\w-]+\.[\w-]+\.[\w-]+/i;
return value.replace(regex, 'id_token=*');
};
}
Specify your health endpoints in order to log a minimum subset of information,
for these inbound_requests. Defaults to [].
This may be useful when: You have a load balancer or other system that pings your server at a specific end-point,
periodically, to determine the health of your server, and you do not want to log much details regarding these requests.
Example
`js`
{
health: [
{
path: '/health',
method: 'GET'
}
]
}
Enable outbound HTTP traffic logs. Defaults to true.
Example:
`js`
{
outbound: {
enabled: true
}
}
Enable outbound_request HTTP traffic logging. Defaults to true.
This option can be used to truncate values JSON body of the outbound POST requests to a specified length. Defaults to undefined.POST
To use this option, the request's body should be a valid JSON.
Example:
`js`
{
outbound: {
maxBodyValueChars: 1024
}
}
This option can be used to prevent specific outbound paths to be logged.
Defaults to [].
Example:
`js`
{
outbound: {
blacklistedPathRegex: /\/health/
}
}
outbound.request.obfuscatedHeaders
This option can be used to prevent specific URL paths from being logged.
Every request that carries a header with a key that matches the values
will obfuscate the URL path when logging.
Defaults to 'X-Riviere-obfuscate'
Example:
`js`
{
outbound: {
obfuscateHrefIfHeaderExists: 'X-Riviere-obfuscate'
}
}
Theis is a Header key for the request id header.
Defaults to: X-Riviere-Id.riviere
If you already use a request id header you may need to set this options.
For example for Heroku deployments,
you most often want to set the traceHeaderName to: X-Request-Id
(https://devcenter.heroku.com/articles/http-request-id)
Example:
`js`
{
traceHeaderName: 'X-Request-Id'
}
---
MIT
(!see LICENCE)