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

@gipo355/nest-pino-logger

v0.0.8

Published

NestJS Pino Logger Module with HTTP logging and loki-grafana

Downloads

5

Readme

nest-pino-logger

Work in progress

Ready made Pino logger for NestJS

includes multi stream transports with pino-loki

Loki

uses pino-loki requires loki promtail and grafana

example docker-compose.yml

version: '3.9'
services:
  loki:
    image: grafana/loki:3.0.0
    # profiles: [full]
    ports:
      - '3100:3100'
    command: -config.file=/etc/loki/local-config.yaml
  promtail:
    # profiles: [full]
    image: grafana/promtail:3.0.0
    volumes:
      - /tmp/loki/promtail/var/log:/var/log
    command: -config.file=/etc/promtail/config.yml
  grafana:
    # profiles: [full]
    environment:
      - GF_PATHS_PROVISIONING=/etc/grafana/provisioning
      - GF_AUTH_ANONYMOUS_ENABLED=true
      - GF_AUTH_ANONYMOUS_ORG_ROLE=Admin
    entrypoint:
      - sh
      - -euc
      - |
        mkdir -p /etc/grafana/provisioning/datasources
        cat <<EOF > /etc/grafana/provisioning/datasources/ds.yaml
        apiVersion: 1
        datasources:
        - name: Loki
          type: loki
          access: proxy
          orgId: 1
          url: http://loki:3100
          basicAuth: true
          isDefault: true
          version: 1
          editable: false
        EOF
        /run.sh
    image: grafana/grafana:latest
    ports:
      - '127.0.0.1:3200:3000'

Pretty

uses pino-pretty

Installation

npm install --save @gipo355/nest-pino-logger

Usage

// main.ts
const app = await NestFactory.create<NestExpressApplication>(AppModule, {
  bufferLogs: true,
});

app.useLogger(app.get(PinoLoggerService));
// app.module
import { PinoLoggerModule } from '@gipo355/nest-pino-logger';

@Module({
    imports: [
        ConfigModule.forRoot(),
        PinoLoggerModule.forRoot({
            pino: {
                pretty: false,
                loki: {
                    host: 'http://localhost:3100',
                    batching: false,
                    basicAuth: {
                        username: '',
                        password: '',
                    },
                    labels: {
                        application: 'nest-pass',
                        http: 'http://localhost:3000',
                    },
                },
            },
        }),
    ],
    controllers: [AppController],
    providers: [
        AppService,
    ],
})
// app.service
constructor(
    private readonly appService: AppService,
    private readonly logger: PinoLoggerService
) {}

TODO

  • allow choosing levels
  • be clear about when and what is logging to stdout
  • allow choosing file or adding remote transport
  • improve documentation