Robust, type-safe and highly configurable logging library for Python
Project description
arlogi - Advanced Logging Library
arlogi is a robust, type-safe logging library for Python that extends the standard logging module with modern features and premium aesthetics.
Features
- Custom TRACE Level: Level 5 logging for ultra-detailed debugging.
- Premium Colored Output: Uses
richfor beautiful, readable console logs with automatic traceback support. - Structured JSON Logging: Out-of-the-box support for JSON logging, perfect for log aggregation systems.
- Module-Specific Configuration: Easily set different log levels for different parts of your application.
- Dedicated Destination Loggers: Log specific events only to JSON or Syslog without cluttering the console.
- Type Safety: Fully type-checked with
LoggerProtocoland supports modern Python types. - SOLID Principles: Focused on maintainability and clear separation of concerns.
Usage
Basic Setup
from arlogi import LoggingConfig, LoggerFactory, get_logger
# 1. Initialize using the modern architecture
config = LoggingConfig(level="INFO")
LoggerFactory._apply_configuration(config)
# 2. Get a logger
logger = get_logger("my_app")
logger.info("Application started")
logger.trace("This won't be visible because level is INFO")
Module-Specific Levels
from arlogi import LoggingConfig, LoggerFactory, TRACE
config = LoggingConfig(
level="INFO",
module_levels={
"my_app.db": "DEBUG",
"my_app.network": TRACE
}
)
LoggerFactory._apply_configuration(config)
JSON and Syslog
from arlogi import LoggingConfig, LoggerFactory
config = LoggingConfig(
use_json=True,
use_syslog=True,
syslog_address="/dev/log"
)
LoggerFactory._apply_configuration(config)
Dedicated Loggers
Sometimes you want to log specific data ONLY to a file or a remote system:
# Logs only to JSON, not to console
audit_logger = get_json_logger("audit")
audit_logger.info("User logged in", extra={"user_id": 123})
# Logs only to Syslog
syslog_logger = get_syslog_logger("security")
syslog_logger.warning("Failed login attempt")
Integration with Other Libraries
arlogi works seamlessly with any third‑party library that uses the standard logging module.
Default INFO when arlogi is not imported
If your application never imports arlogi, the standard logging defaults (WARNING) remain unchanged. To get a simple INFO level without pulling in arlogi, add a tiny bootstrap:
import logging
logging.basicConfig(level=logging.INFO)
Overriding the level when you do use arlogi
Initialize arlogi with a LoggingConfig object early in your program (or set the ARLOGI_LEVEL environment variable). The configuration object allows for fine-grained control over levels and handlers.
Making third‑party libraries respect the chosen level
All libraries that obtain a logger via logging.getLogger(name) inherit the level from the nearest ancestor – usually the root logger configured via LoggingConfig. If a library forces its own level, reset it:
import logging
logging.getLogger("some_lib").setLevel(logging.NOTSET) # inherit from root
Quick bootstrap example
# bootstrap.py
import os, logging, arlogi
from arlogi import LoggingConfig, LoggerFactory
def configure_logging():
if os.getenv("USE_ARLOGI", "0") == "1":
level = os.getenv("ARLOGI_LEVEL", "INFO").upper()
config = LoggingConfig(level=level)
LoggerFactory._apply_configuration(config)
else:
logging.basicConfig(level=logging.INFO)
# main.py
from bootstrap import configure_logging
configure_logging()
With this pattern you get:
- Default INFO when
arlogiis absent. - Full control over the log level when you import
arlogi. - Automatic inheritance for any library that uses
logging.
Using TRACE in your library
If you are developing a library and want to use the TRACE level:
-
The Safe Way (Recommended): Use
logger.log(TRACE, ...)This works regardless of when your library is imported relative toarlogisetup.import logging # You can import TRACE from arlogi, or just define TRACE=5 try: from arlogi import TRACE except ImportError: TRACE = 5 logger = logging.getLogger(__name__) def complex_operation(): logger.log(TRACE, "Step 1 of complex operation...")
-
The method way:
logger.trace(...)This only works ifarlogiis configured before your library creates its logger instance. If your library is imported before setup, you will get anAttributeError.
Lazy Initialization (Safe Use of .trace)
If you must use .trace() in your library but aren't sure if arlogi is setup yet, you can use lazy initialization with LoggerProtocol for type safety:
from arlogi import LoggerProtocol, get_logger
# Use LoggerProtocol for type hinting
_logger: LoggerProtocol | None = None
def log() -> LoggerProtocol:
"""Get or create the logger for this module lazily."""
global _logger
if _logger is None:
# get_logger() returns LoggerProtocol
_logger = get_logger("my_lib.cache")
return _logger
Advanced Configuration
New Configuration Architecture
For more control and type safety, you can use LoggingConfig and LoggerFactory directly. This is the recommended way for advanced users.
from arlogi import LoggingConfig, LoggerFactory
# Create a configuration object
config = LoggingConfig(
level="INFO",
module_levels={"app.db": "DEBUG"},
json_file_name="logs/app.jsonl"
)
# Apply it globally
LoggerFactory._apply_configuration(config)
Legacy Setup (Deprecated)
[!WARNING]
setup_logging()is now considered a legacy helper and is deprecated in favor of theLoggingConfigpattern. It remains available for backward compatibility but may be removed in a future major version.
The setup_logging() helper is still available and internally uses the new architecture:
from arlogi import setup_logging
setup_logging(
level="INFO",
module_levels={"app.db": "DEBUG"},
json_file_name="logs/app.jsonl"
)
Console Styling
By default, arlogi uses a clean, modern style for console output. You can further customize this:
from arlogi import LoggingConfig, LoggerFactory
config = LoggingConfig(
show_time=True, # Enable/disable timestamp
show_level=True, # Enable/disable level name
show_path=False, # Enable/disable source file path
)
LoggerFactory._apply_configuration(config)
To make logs start from the very beginning of the line, arlogi defaults show_time to False.
Color Schemes
arlogi comes with a refined default color scheme:
- TRACE / DEBUG: Grey
- INFO: Bright White
- WARNING: Yellow
- ERROR / CRITICAL: Red
You can customize these by instantiating ColoredConsoleHandler with a level_styles dictionary, or by modifying the default behavior in setup_logging (coming soon as a direct parameter).
Development
Run tests with pytest:
uv run pytest
Check types:
uv run ty check src/
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file arlogi-0.601.4.tar.gz.
File metadata
- Download URL: arlogi-0.601.4.tar.gz
- Upload date:
- Size: 139.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: uv/0.5.17
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
3fdc187d39767b05fd2a0aedbb774b0e19649c7e5d550634f0f74686a88f07b0
|
|
| MD5 |
be14ad2d9af060868aaa2220927a70ff
|
|
| BLAKE2b-256 |
b53ad1e69e1be997278b9d6914fc5d138196808cfa72a5bf4eaf04311cd9f46e
|
File details
Details for the file arlogi-0.601.4-py3-none-any.whl.
File metadata
- Download URL: arlogi-0.601.4-py3-none-any.whl
- Upload date:
- Size: 20.0 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: uv/0.5.17
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
7aa6039f03b7e0d74fc4e800015427c6095600e68d26fcd14f369266bb3ac7a0
|
|
| MD5 |
a47f7d24938eea8a7949a51694092d28
|
|
| BLAKE2b-256 |
033991b83ce7eb65c6b25be9035af0693ced3be5dba0b013efce71a2f4794ebf
|