Logger

This document describes the environment variables available for configuring log levels across ICC (Intelligent Command Center) services.

Overview

ICC uses environment variables to control logging verbosity for individual microservices. Each service can have its own log level, allowing fine-grained control over logging output in different environments.

Environment Variables

Services with Configurable Log Levels

Service	Environment Variable	Default Value	Description
Main (API Gateway)	PLT_MAIN_LOGGER_LEVEL	warn	Controls logging for the main API gateway service
Control Plane	PLT_CONTROL_PLANE_LOG_LEVEL	warn	Controls logging for Kubernetes integration and app management
Cron	PLT_CRON_LOGGER_LEVEL	warn	Controls logging for scheduled job management
Scaler	PLT_SCALER_LOGGER_LEVEL	warn	Controls logging for autoscaling operations
Risk Service	PLT_RISK_SERVICE_LOGGER_LEVEL	warn	Controls logging for OpenTelemetry traces and risk assessment
Risk Cold Storage	PLT_COLD_STORAGE_LOGGER_LEVEL	warn	Controls logging for cold storage operations
Trafficante	PLT_TRAFFICANTE_LOGGER_LEVEL	warn	Controls logging for the trafficante service

Available Log Levels

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

Development Environment

For verbose logging during development:

export PLT_MAIN_LOGGER_LEVEL=debug
export PLT_CONTROL_PLANE_LOG_LEVEL=debug
export PLT_SCALER_LOGGER_LEVEL=trace

Production Environment

For minimal logging in production (default):

export PLT_MAIN_LOGGER_LEVEL=warn
export PLT_CONTROL_PLANE_LOG_LEVEL=warn
export PLT_CRON_LOGGER_LEVEL=warn

Debugging Specific Service

To debug only the scaler service:

export PLT_SCALER_LOGGER_LEVEL=debug
# Keep other services at warn level

Special Configurations

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

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