Logger

Ts.ED has its own logger available through @tsed/logger package.

Installation

npm

npm install --save @tsed/logger

yarn

yarn add @tsed/logger

pnpm

pnpm add @tsed/logger

bun

bun add @tsed/logger

Features

Ts.ED logger supports many features, and is optimized to be used in production:

• ContextLogger, in production mode, caches all request logs until the response is sent to your consumer. See request logger section bellow.
• Layouts support,
• Appenders support;

Configuration

Logger can be configured through the Configuration decorator:

Props	Description
logger.level	Change the default log level displayed in the terminal. Values: debug, info, warn or error. By default: info.
logger.logRequest	Log all incoming requests. By default, it's true and prints the configured logger.requestFields.
logger.requestFields	Fields displayed when a request is logged. Possible values: reqId, method, url, headers, body, query,params, duration. This option has effect only on the info level.
logger.reqIdBuilder	A function called for each incoming request to create a request id.
logger.jsonIndentation	The number of space characters to use as white space in JSON output. Default is 2 (0 in production).
logger.disableRoutesSummary	Disable routes table displayed in the logger.
logger.format	Specify log format. Example: %[%d{[yyyy-MM-dd hh:mm:ss,SSS}] %p%] %m. See @tsed/logger configuration.
logger.ignoreUrlPatterns	(String or RegExp) List of patterns to ignore logged request according to the request.url.

WARNING

It's recommended to disable logRequest in production. Logger has a cost on the performance.

Layouts and Appenders

Layouts

You can configure a layout to format the log output. The following layouts are available:

Name	Description
Basic layout	Basic layout will output the timestamp, level, category, followed by the formatted log event data.
Colored layout	This layout is the same as basic, except that the timestamp, level and category will be colored according to the log event's level
Dummy layout	This layout only outputs the first value in the log event's data.
Message layout	Use a simple message format to display log
Json layout	Display log to JSON format
Pattern layout	Use custom pattern to format log
Custom layout	logging to stdout or stderr with a custom layout.

Appenders

You can configure an appender to send log events to a destination. The following appenders are available:

Name	Description
Connect	allows connecting Ts.ED logger with another logger.
Console	log to the console.
File	log to a file.
File date	log to a file with configurable log rolling based on file size or date.
Stdout	log to stdout.
Stderr	log to stderr.
Insight	log to Insight.
LogEntries	log to LogEntries.
LogStash HTTP	log to LogStash.
LogStash UDP	log to LogStash.
Loggly	log to Loggly.
RabbitMQ	log to RabbitMQ.
Seq	log to Seq.
Slack	log to Slack.
Smtp	log to SMTP.

TIP

You can create your own layout/appender:

• Customize appender (chanel),
• Customize layout

Use Json Layout in production

You add this code to switch the logger to Json layout in production mode:

import {env} from "@tsed/core";
import {Configuration} from "@tsed/di";
import {$log} from "@tsed/logger";
import "@tsed/platform-express";

export const isProduction = process.env.NODE_ENV === Env.PROD;

if (isProduction) {
  $log.appenders.set("stdout", {
    type: "stdout",
    levels: ["info", "debug"],
    layout: {
      type: "json"
    }
  });
  $log.appenders.set("stderr", {
    levels: ["trace", "fatal", "error", "warn"],
    type: "stderr",
    layout: {
      type: "json"
    }
  });
}

@Configuration({
  logger: {
    disableRoutesSummary: isProduction // remove table with routes summary
  }
})
export class Server {}

This configuration will display the log as following:

{"startTime":"2017-06-05T22:23:08.479Z","categoryName":"json-test","data":["this is just a test"],"level":"INFO","context":{}}

It's more useful if you planed to parse the log with LogStash or any log tool parser.

Inject logger

Logger can be injected in any injectable provider as follows:

import {Logger} from "@tsed/logger";
import {Injectable, Inject} from "@tsed/di";

@Injectable()
export class MyService {
  @Inject()
  logger: Logger;

  $onInit() {
    this.logger.info("Hello world");
  }
}

TIP

Prefer the ContextLogger usage if you want to attach your log the current request. See the next section.

Request logger

For each Request, a logger will be attached to the PlatformContext and can be used like here:

import {Controller} from "@tsed/di";
import {Logger} from "@tsed/logger";
import {Context} from "@tsed/platform-params";
import {Get} from "@tsed/schema";
import {MyService} from "../services/MyService";

@Controller("/")
class MyController {
  @Inject()
  myService: MyService;

  @Get("/")
  get(@Context() ctx: Context) {
    ctx.logger.info({customData: "test"}); // parameter is optional
    ctx.logger.debug({customData: "test"});
    ctx.logger.warn({customData: "test"});
    ctx.logger.error({customData: "test"});
    ctx.logger.trace({customData: "test"});

    // forward ctx object to the service and use logger inside.
    // All request
    myService.doSomething("test", ctx);
  }
}

import {PlatformContext} from "@tsed/platform-http";
import {Injectable, Inject} from "@tsed/di";

@Injectable()
export class MyService {
  doSomething(input: string, ctx: PlatformContext) {
    ctx.logger.info({event: "test", input});
  }
}

TIP

All log use through ctx.logger will be associated with the uniq request id generated by Ts.ED.

TIP

ContextLogger, in production mode, caches all request logs until the response is sent to your consumer.

A call with one of these methods will generate a log according to the logger.requestFields configuration:

[2017-09-01 11:12:46.994] [INFO ] [TSED] - {
  "status": 200,
  "reqId": 1,
  "method": "GET",
  "url": "/api-doc/swagger.json",
  "duration": 92,
  "headers": {
    "host": "0.0.0.0:8001",
    "connection": "keep-alive",
    "upgrade-insecure-requests": "1",
    "user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36",
    "accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8",
    "accept-encoding": "gzip, deflate",
    "accept-language": "fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4"
  },
  "body": {},
  "query": {},
  "customData": "test"
}

You can configure the displayed fields from the server configuration:

import {Configuration} from "@tsed/di";

@Configuration({
  logger: {
    requestFields: ["reqId", "method", "url", "headers", "body", "query", "params", "duration"]
  }
})
export class Server {}

or you can override the middleware with OverrideProvider.

Example:

import {OverrideProvider} from "@tsed/di";
import {Context, PlatformLogMiddleware} from "@tsed/common";

@OverrideProvider(PlatformLogMiddleware)
export class CustomPlatformLogMiddleware extends PlatformLogMiddleware {
  public use(@Context() ctx: Context) {
    // do something

    return super.use(ctx); // required
  }

  protected requestToObject(ctx: Context) {
    const {request} = ctx;

    // NOTE: request => PlatformRequest. To get Express.Request use ctx.getRequest<Express.Request>();
    return {
      method: request.method,
      url: request.url,
      headers: request.headers,
      body: request.body,
      query: request.query,
      params: request.params
    };
  }
}

Another example to redact some fields:

import {Context, OverrideProvider} from "@tsed/di";
import {PlatformLogMiddleware} from "@tsed/platform-log-middleware";

@OverrideProvider(PlatformLogMiddleware)
export class CustomPlatformLogMiddleware extends PlatformLogMiddleware {
  attributesToHide = ["password", "client_secret"];

  private redactAttributes(body: any): any {
    if (body) {
      for (const attribute of this.attributesToHide) {
        if (body[attribute]) {
          body[attribute] = "[REDACTED]";
        }
      }
    }
    return body;
  }

  requestToObject(ctx: Context): any {
    const {request} = ctx;

    return {
      method: request.method,
      url: request.url,
      route: request.route,
      headers: request.headers,
      body: this.redactAttributes(request.body),
      query: request.query,
      params: request.params
    };
  }
}

Shutdown logger

Shutdown returns a Promise that will be resolved when `@tsed/logger has closed all appenders and finished writing log events. Use this when your program exits to make sure all your logs are written to files, sockets are closed, etc.

import {$log} from "@tsed/logger";

$log.shutdown().then(() => {
  console.log("Complete");
});