Awesome
<div align="center"> <h1>@kasa/koa-request-id</h1> </div> <p align="center"> A middleware that generates a unique Request ID for every incoming HTTP request in Koa. </p> <div align="center"> <a href="https://circleci.com/gh/kasa-network/koa-request-id"> <img alt="CircleCI" src="https://circleci.com/gh/kasa-network/koa-request-id.svg?style=shield" /> </a> <a href="https://coveralls.io/github/kasa-network/koa-request-id"> <img src="https://coveralls.io/repos/github/kasa-network/koa-request-id/badge.svg" alt='Coverage Status' /> </a> <a href="https://badge.fury.io/js/@kasa/koa-request-id"> <img alt="npm version" src="https://img.shields.io/npm/v/@kasa/koa-request-id.svg" /> </a> <a href="https://david-dm.org/kasa-network/koa-request-id"> <img alt="npm" src="https://img.shields.io/david/kasa-network/koa-request-id.svg?style=flat-square" /> </a> <a href="https://opensource.org/licenses/mit-license.php"> <img alt="MIT Licence" src="https://badges.frapsoft.com/os/mit/mit.svg?v=103" /> </a> <a href="https://github.com/ellerbrock/open-source-badge/"> <img alt="Open Source Love" src="https://badges.frapsoft.com/os/v1/open-source.svg?v=103" /> </a> </div> <br />Installation
# Using NPM
$ npm install --save @kasa/koa-request-id
# Using Yarn
$ yarn add @kasa/koa-request-id
Dependencies
Usage
Use koa-request-id
as a middleware for a koa app. By default, it generates a unique uuid (v4) and exposes it on the response via the X-Request-Id
header. The id is also saved as part of the request state.
In the following example, the generated uuid is manually exposed on the body for debugging purposes:
const Koa = require('koa');
const requestId = require('@kasa/koa-request-id');
const app = new Koa();
app.use(requestId());
app.use(async ctx => {
ctx.body = ctx.state.reqId;
});
app.listen(3000);
Execute a request to the running app:
❯ curl -v http://localhost:3000
< HTTP/1.1 200 OK
< X-Request-Id: a78598a4-6537-45eb-811c-fdc59602a54c
a78598a4-6537-45eb-811c-fdc59602a54c
Sometimes it is also useful to pass a custom id via a request header, specifically in tracking requests on the distributed system. Please note that the input id is not sanitized, so the usual precautions apply.
Using the above snippet to send a custom via the default X-Request-Id
header:
❯ curl -v -H 'X-Request-Id: foobar' http://localhost:3000
< HTTP/1.1 200 OK
< X-Request-Id: foobar
foobar
API
Creating an middleware
You can create a new request id middleware by passing the relevant options to requestId
;
// With default options
const middleware = requestId({
query: null,
header: 'X-Request-Id',
exposeHeader: 'X-Request-Id',
generator: require('uuid/v4')
});
Middleware Configuration
These are the available config options for the middleware. All is optional. The middleware try to get the request id from X-Request-Id
request header or generate a new request id using uuidv4
generator. Then, the request id will be set into ctx.state.reqId
Koa context state object and X-Request-Id
response header if any option is not specified.
{
// Request query name to get the forwarded request id
query: 'reqId',
// Request header name to get the forwarded request id
header: 'X-Transaction-Id',
// Response header name
exposeHeader: 'X-Transaction-Id',
// Function to generate request id
generator: () => Date.now().toString()
}
Contributing
Bug Reports & Feature Requests
Please use the issue tracker to report any bugs or ask feature requests.
License
Provided under the terms of the MIT License.
Copyright © 2018-2019, Kasa.