About SmooAI
SmooAI is an AI-powered platform for helping businesses multiply their customer, employee, and developer experience.
Learn more on smoo.ai
SmooAI Packages
Check out other SmooAI packages at smoo.ai/open-source
About smooai-logger (Python)
The missing piece for AWS & Browser logging - A contextual logging system that automatically captures the full execution context you need to debug production issues, without the manual setup.
Python Package
This is the Python port of @smooai/logger, mirroring the TypeScript API for backend services. It provides the same contextual logging capabilities with automatic AWS context capture and correlation tracking.
Why smooai-logger?
Ever spent hours debugging an AWS service in production, only to realize you're missing critical context? Traditional loggers give you the message, but not the story.
smooai-logger automatically captures:
For AWS Services:
- 📍 Exact code location - File, line number, and call stack for every log
- 🔗 Request journey - Correlation IDs that follow requests across services
- ⚡ AWS context - Service-specific metadata and execution details
- 🌐 HTTP details - Headers, methods, status codes from API Gateway
- 📬 Message context - SQS attributes, EventBridge events, SNS messages
- 🔧 Service integration - Lambda, ECS, Fargate, EC2, and more
Install
pip install smooai-logger
or with uv:
uv add smooai-logger
The Power of Automatic Context
See Where Your Logs Come From
Every log entry includes the exact location in your code:
from smooai_logger import AwsServerLogger
logger = AwsServerLogger()
logger.info("User created")
# Output includes:
{
"callerContext": {
"stack": [
"at UserService.create_user (/src/services/user_service.py:42:16)",
"at process_request (/src/handlers/user_handler.py:15:23)",
"at handler (/src/index.py:8:10)"
]
}
}
No more guessing which function logged what - the full execution path is right there.
Track Requests Across Services
Correlation IDs automatically flow through your entire system:
# Service A: API Gateway Handler
logger.add_lambda_context(event, context)
logger.info("Request received") # Correlation ID: abc-123
# Service B: SQS Processor (automatically extracts ID)
logger.add_sqs_record_context(record)
logger.info("Processing message") # Same Correlation ID: abc-123
# Service C: Another Lambda (receives via HTTP header)
logger.info("Completing workflow") # Still Correlation ID: abc-123
Production-Ready Examples
AWS Lambda with API Gateway
from smooai_logger import AwsServerLogger, Level
logger = AwsServerLogger(name="UserAPI")
def handler(event, context):
logger.add_lambda_context(event, context)
try:
user = create_user(event["body"])
logger.info("User created successfully", {"userId": user.id})
return {"statusCode": 201, "body": json.dumps(user)}
except Exception as error:
logger.error("Failed to create user", error, {
"body": event["body"],
"headers": event["headers"],
})
raise error
AWS ECS/Fargate Services
import os
from smooai_logger import AwsServerLogger, Level
logger = AwsServerLogger(
name="OrderService",
level=Level.INFO,
)
# Automatically captures container metadata
@app.post('/orders')
async def create_order(request):
logger.add_context({
"taskArn": os.environ.get("ECS_TASK_ARN"),
"containerName": os.environ.get("ECS_CONTAINER_NAME"),
})
logger.info("Processing order", {
"orderId": request.json["orderId"],
"amount": request.json["amount"],
})
SQS Message Processing
def sqs_handler(event):
for record in event["Records"]:
logger.add_sqs_record_context(record)
logger.info("Processing order", {
"messageId": record["messageId"],
"attempt": record["attributes"]["ApproximateReceiveCount"],
})
# Logger maintains context throughout async operations
process_order(record["body"])
Advanced Features
Smart Error Handling
Errors are automatically serialized with full context:
try:
risky_operation()
except Exception as error:
logger.error("Operation failed", error, {"context": "additional-info"})
# Includes: error message, stack trace, error type, and your context
Flexible Context Management
# Add user context that persists across logs
logger.add_user_context({"id": "user-123", "role": "admin"})
# Add telemetry for performance tracking
logger.add_telemetry_fields({"duration": 150, "operation": "db-query"})
# Add custom context for specific logs
logger.info("Payment processed", {
"amount": 99.99,
"currency": "USD",
})
Local Development Features
Pretty Printing
logger = AwsServerLogger(
pretty_print=True # Readable console output for development
)
Automatic Log Rotation
Logs are automatically saved to disk in development with smart rotation:
# Auto-enabled in local environments
# Saves to .smooai-logs/ with ANSI colors for easy reading
logger = AwsServerLogger(
rotation={
"size": "10M", # Rotate at 10MB
"interval": "1d", # Daily rotation
"compress": True, # Gzip old logs
}
)
Configuration
Log Levels
TRACE- Detailed debugging informationDEBUG- Diagnostic informationINFO- General operational informationWARN- Warning conditionsERROR- Error conditionsFATAL- Critical failures
Context Presets
MINIMAL- Essential context onlyFULL- All available context (default)
Built With
- Python 3.8+ - Full type hints support
- AWS SDK Integration - Native support for Lambda, ECS, EC2, and more
- Automatic environment detection
- Smart log rotation
Related Packages
- @smooai/logger - TypeScript/JavaScript version
- smooai-logger (Rust) - Rust version
Development
uv run poe install-dev
uv run pytest
uv run poe lint
uv run poe lint:fix # optional fixer
uv run poe format
uv run poe typecheck
uv run poe build
Set UV_PUBLISH_TOKEN before running uv run poe publish to upload to PyPI.
Contact
Brent Rager
Smoo Github: https://github.com/SmooAI
License
MIT © SmooAI
Metadata
Release files for smooai-logger 4.5.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| smooai_logger-4.5.4.tar.gz | 44.8 kB | Without provenance | Details for smooai_logger-4.5.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| smooai_logger-4.5.4-py3-none-any.whl | Python 3 | none | any | Details for smooai_logger-4.5.4-py3-none-any.whl |
Total release size: 65.0 kB
Release files / smooai_logger-4.5.4.tar.gz
| Download URL | smooai_logger-4.5.4.tar.gz |
|---|---|
| Size | 44.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53fb338f67b8baae71b5577594143256dbd609d8dc9a25c358ec347d9a1ba021
|
|
BLAKE2b-256 checksum How to use checksums |
c8e92adf7993de9ea8d0e7cb18d7dd9da5e7b21d206c943ab9f9e97a30341847
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / smooai_logger-4.5.4-py3-none-any.whl
| Download URL | smooai_logger-4.5.4-py3-none-any.whl |
|---|---|
| Size | 20.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
246c67bf2c7ba5d17ee3c3c4a22b948b286dc02f5c0c2c3ebcc84aa923c8b35d
|
|
BLAKE2b-256 checksum How to use checksums |
b500e1a970ae8b1789adb909bf1d6c2db66b9499fa596c704bc6721af9a26b80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for smooai-logger 4.5.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.