📘
@node-test/bus
  • @node-ts/bus
  • Getting started
    • Installation
    • Handling messages
    • Shutting down cleanly
  • Reference
    • Bus
    • BusConfiguration
    • BusInstance
  • Getting help
  • Guide
    • Messages
      • Events
      • Commands
      • System messages
    • Message attributes
      • Correlation id
      • Attributes
      • Sticky attributes
    • Workflows
      • Creating a workflow
      • Starting
      • Handling
      • State
      • Completing
      • Example
    • Transports
      • RabbitMQ
      • Amazon SQS
      • Redis
      • Custom transports
    • Persistence
      • Postgres
      • MongoDB
      • Creating a persistence
    • Serializers
      • Class serializer
    • Loggers
      • Custom loggers
    • Middleware
    • Lifecycle hooks
    • Retry Strategies
    • Dependency injection
    • Long running processes
Powered by GitBook
On this page

Was this helpful?

  1. Guide

Loggers

PreviousClass serializerNextCustom loggers

Last updated 3 years ago

Was this helpful?

@node-ts/bus-core by default uses the library in order to log details to STDOUT. All log messages that originate from this library are named with a @node-ts/ prefix. In order to get full debug output, set the DEBUG environment variable to @node-ts/*

For example:

DEBUG="@node-ts/*" npm run dev

If you want to use your own logging provider and change the output format etc, this can be changed with any other logger by providing an adapter layer for a .

debug
custom logger