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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nestjslatam/aop.aspects.telemetry

v1.1.0

Published

Aspecto de trazas con OpenTelemetry para @nestjslatam/aop

Readme

@nestjslatam/aop.aspects.telemetry

Aspecto de trazas con OpenTelemetry para @nestjslatam/aop.

No tiene equivalente en la librería .NET BeyondNet.Aop: es la cara de trazas del mismo OnMethodBoundaryAspect que impulsa a LoggerAspect.

@opentelemetry/api es una peer dependency.

npm install @nestjslatam/aop.aspects.telemetry @opentelemetry/api

Registro

import { AopModule } from '@nestjslatam/aop.nestjs';
import { TraceAspect } from '@nestjslatam/aop.aspects.telemetry';

@Module({
  imports: [
    AopModule.forRoot({ configure: (builder) => builder.addAspect(TraceAspect) }),
  ],
})
export class AppModule {}

El aspecto usa el tracer provider registrado globalmente, así que el SDK se configura como siempre (NodeSDK, @opentelemetry/auto-instrumentations-node, o un instrumentation.ts cargado antes que la aplicación).

Uso

@Trace()
@LogMethod()
@Retry({ maxAttempts: 3 })
async pay(orderId: string): Promise<Receipt> { ... }

@Trace() se ejecuta como el más externo por defecto (order: 0), de modo que un único span cubre el logging y todos los reintentos. Opciones: name, kind, tracer, attributes, resolveAttributes(args, joinPoint), recordException y order.

@Trace({
  name: 'orders.pay',
  kind: SpanKind.SERVER,
  resolveAttributes: (args) => ({ 'order.id': args[0] }),
})

Cada span lleva los atributos de convención semántica code.function y code.namespace, se cierra tanto en éxito como en fallo, y recibe SpanStatusCode.ERROR más la excepción registrada cuando el método lanza. El error siempre se relanza: el aspecto observa, no traga.

Correlación con los logs

Mientras el método corre, el span es el span activo, así que todo lo que se llame dentro cuelga de la misma traza, y el aspecto escribe traceId / spanId en el join point. LoggerAspect los recoge, lo que significa:

  • PinoSink los emite como campos estructurados.
  • NestLoggerSink añade [TraceId: ..., SpanId: ...] al mensaje.

Eso es lo que permite saltar en Grafana de una línea de Loki a la traza en Tempo.

{"level":20,"msg":"Start Call.","className":"OrdersService","methodName":"pay","traceId":"4bf92f…","spanId":"00f067…"}

Documentación

Guía How-To: trazas · Manual de uso

Licencia

MIT