Skip to main content
Send logs to external services using custom transports. Transports work alongside built-in console and file logging. Looking for Axiom, Better Stack, ClickHouse, Datadog, HyperDX, Loki, OTLP, PostHog, or Sentry? Built-in adapters cover those — with batching, retries, and credential handling included. Custom transports are for everything else.

Output Behavior

Logixlysia supports three types of logging outputs:
  1. Console Logging - Built-in console output
  2. File Logging - Built-in file output
  3. Transport Logging - Custom external services

Controlling Outputs

  • Default: Console + File (if logFilePath is set) + Transports
  • disableInternalLogger: true: Disables console logging only
  • disableFileLogging: true: Disables file logging only
  • useTransportsOnly: true: Disables both console and file, uses only transports

Basic Transport

External Services

Elasticsearch

MongoDB

Slack

Multiple Transports

Transport-Only Logging

Best Practices

  • Handle transport errors gracefully
  • Implement retry logic for critical transports
  • Use async transports for better performance
  • Secure transport credentials
  • Avoid logging secrets or PII
  • Use useTransportsOnly for production environments where you only want external logging