Skip to content
Platformatic Platformatic Intelligent Command Center (ICC)

Logger

Overview

Section titled “Overview”

ICC uses a single setting to control the logging of all sub-services.

Configuration

Section titled “Configuration”

The environment variable to set is PLT_ICC_LOGGER_LEVEL.

When installing with Helm, set services.icc.log_level.

The following log levels are supported, from least to most verbose:

  • fatal - Only fatal errors
  • error - Errors and above
  • warn - Warnings and above (default)
  • info - Informational messages and above
  • debug - Debug messages and above
  • trace - All messages including trace level

Usage Examples

Section titled “Usage Examples”

Development Environment

Section titled “Development Environment”

For verbose logging during development:

Terminal window
export PLT_ICC_LOGGER_LEVEL=debug

Production Environment

Section titled “Production Environment”

For minimal logging in production (default):

Terminal window
export PLT_ICC_LOGGER_LEVEL=warn

Special Configurations

Section titled “Special Configurations”

Health Check Route

Section titled “Health Check Route”

The main service has a special configuration for the health check route (/health) that sets its log level to error to prevent health check requests from cluttering the logs.

Best Practices

Section titled “Best Practices”
  1. Production: Use warn or error levels to minimize log volume
  2. Development: Use info or debug for better visibility
  3. Debugging: Use trace for specific services when troubleshooting
  4. Performance: Higher log levels (trace, debug) can impact performance; use sparingly in production