npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@flopezluksenberg/nestjs-trace-id

v1.0.0

Published

NestJS Module that create/use and share a trace id object

Downloads

3

Readme

NestJs Trace ID

NestJs module that creates or use an identifier for each request and also send this to other microservices through the @nestjs/axios layer, in order to have a distributed identifier. Really usefull when you need to follow specific workflow of a request in logs.

This uses the AsyncLocalStorage and was inspired in this repository https://github.com/abonifacio/nestjs-request-context

Usage

In your app.module.ts file do the following

...
import { TraceIdModule } from 'nestjs-trace-id';
...
@Module({
  imports: [
    ...
      TraceIdModule,
    ...
  ], 
  providers: [...],
  controllers: [..],
})
export class AppModule {}

Once you added the module, you can set the header X-Trace-Id in your request or it will be generated automatically using a random UUID. This header will be propagated to the requests made by httpService and the generated trace id will be available on the final response too.

Examples

Let's say that your NestJs app has a route under https://localhost:4000/somewhere:

// Example of autogenerated uuid
curl -I localhost:4000/somewhere
HTTP/1.1 200 OK
X-Trace-Id: 8120dbf5-9054-4516-b602-6a6bd118ce5a
X-Powered-By: Express
Content-Type: application/json; charset=utf-8
Content-Length: 43
ETag: W/"2b-hGShxOkieaAVDloBubJVM+h58D8"
Date: Fri, 09 Sep 2022 18:48:20 GMT
Connection: keep-alive
Keep-Alive: timeout=5

// Example of custom trace id
curl -H "X-Trace-Id: Example" -I http://localhost:4000/somewhere
HTTP/1.1 200 Ok
X-Trace-Id: Example
X-Powered-By: Express
Content-Type: application/json; charset=utf-8
Content-Length: 43
ETag: W/"2b-hGShxOkieaAVDloBubJVM+h58D8"
Date: Fri, 09 Sep 2022 18:51:00 GMT
Connection: keep-alive
Keep-Alive: timeout=5

Miscelaneus

Setup traceId in your Pino Logs

If you are using Pino for logging, you can setup the traceId in the logs in order to help while you're debugging your application:


...
import { TraceIdModule, TraceIdMiddleware } from 'nestjs-trace-id';
...
@Module({
  imports: [
    ...
      TraceIdModule,
      LoggerModule.forRoot({
        ...
        pinoHttp: {
          ...
          customProps: (req: Request) => ({
            traceId: req[TraceIdMiddleware.Header],
          }),
          ...
        },
        ...
      }),
    ...
  ], 
  providers: [...],
  controllers: [..],
})
export class AppModule {}

Accessing to the trace id

You can also access to request identifier if you need to pass to somewhere

import { TraceIdMiddleware } from './trace-id.middleware';

@Controller('/somewhere')
export class SomeController {
...

  @Get()
  someName(@Req() req) {
    ...
    const traceId = req[TraceIdMiddleware.Header]
    ...
  }
}

Release Notes

1.0.0

First version