> Use when implementing logging, error tracking, or monitoring in Frappe v14-v16. Covers frappe.logger() for file-based logging, frappe.log_error() for Error Log DocType entries, request logging, Sentry integration, and production logging patterns. Prevents common mistakes with print(), swapped log_error arguments, and sensitive data. monitor, request logging, error tracking, debug, production.
npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging
| Mechanism | Storage | Use For |
|-----------|---------|---------|
| frappe.logger() | File (rotating) | Application logging, debug info, audit trails |
| frappe.log_error() | Database (Error Log DocType) | Errors visible in admin UI, persistent tracking |
| frappe.log() / frappe.errprint() | stderr / request-scoped | Quick debugging only (NOT for production) |
Need to log something?
│
├─ Application logging (info, debug, warnings)?
│ └─ frappe.logger("my_module").info("message")
│ → Writes to sites/{site}/logs/my_module.log
│
├─ Error that admins should see in Desk UI?
│ └─ frappe.log_error(title="Short desc", message=traceback)
│ → Creates Error Log document (queryable, auto-cleanup)
│
├─ Quick debug during development?
│ └─ frappe.errprint(variable) — shows in console
│ → NEVER leave in production code
│
├─ Track all HTTP requests?
│ └─ Set enable_frappe_logger: true in site_config.json
│ → Logs to frappe.web.log
│
├─ Performance monitoring?
│ └─ Set monitor: true in site_config.json
│ → Logs to monitor.json.log (JSON, per-request metrics)
│
└─ External error tracking (Sentry)?
└─ Set FRAPPE_SENTRY_DSN environment variable
→ Auto-captures unhandled exceptions
# Get a logger for your module (ALWAYS specify module name)
logger = frappe.logger("my_app")
# Standard Python logging levels
logger.debug("Detailed diagnostic info")
logger.info("Normal operations: processed 50 records")
logger.warning("Something unexpected but recoverable")
logger.error("Operation failed", exc_info=True)
logger.critical("System-level failure")
# Full signature
frappe.logger(
module=None, # Logger name + log filename
with_more_info=False, # Auto-log request form_dict
allow_site=True, # Log under site's logs/ directory
filter=None, # Custom logging.Filter
max_size=100_000, # Max bytes per log file (100KB default)
file_count=20 # Rotated files retained (20 default)
)
Log location: sites/{site}/logs/{module}.log
Rotation: RotatingFileHandler — 100KB per file, 20 backups (~2MB total per logger)
| Mode | Level | Effect |
|------|-------|--------|
| Development (_dev_server) | WARNING | Debug/info suppressed |
| Production | ERROR | Only errors and above |
# Change level dynamically
frappe.utils.logger.set_log_level("DEBUG")
# ALWAYS use keyword arguments (title/message can swap otherwise)
frappe.log_error(
title="Payment gateway timeout", # Short description (140 chars max)
message=frappe.get_traceback(), # Full error details
reference_doctype="Payment Entry", # Related DocType
reference_name="PE-00001" # Related document
)
# Minimal — auto-captures current traceback
try:
risky_operation()
except Exception:
frappe.log_error(title="Operation failed")
Error Log cleanup: Auto-deletes after 30 days. Manual: frappe.whitelist: clear_error_logs()
Unhandled exceptions (HTTP 500+) are automatically logged to Error Log.
Excluded from auto-capture:
frappe.AuthenticationErrorfrappe.CSRFTokenErrorfrappe.SecurityExceptionfrappe.InReadOnlyMode| Key | Value | Effect |
|-----|-------|--------|
| enable_frappe_logger | true | HTTP request logging → frappe.web.log |
| logging | 2 | Log all SQL queries (debug only!) |
| monitor | true | Request/job metrics → monitor.json.log |
| disable_error_snapshot | true | Disable auto-capture of exceptions |
| Variable | Effect |
|----------|--------|
| FRAPPE_STREAM_LOGGING=1 | Log to stderr instead of files |
| FRAPPE_SENTRY_DSN=<dsn> | Enable Sentry error tracking |
| ENABLE_SENTRY_DB_MONITORING | Track SQL queries in Sentry |
| SENTRY_TRACING_SAMPLE_RATE | Performance tracing rate (0.0-1.0) |
| File | Content |
|------|---------|
| logs/web.error.log | HTTP errors (supervisor) |
| logs/web.log | Gunicorn stdout |
| logs/worker.error.log | Background job errors |
| logs/frappe.log | Default frappe logger |
| logs/frappe.web.log | HTTP request metadata |
| logs/monitor.json.log | Performance metrics (JSON) |
| sites/{site}/logs/*.log | Per-site application logs |
| NEVER | ALWAYS | Why |
|-------|--------|-----|
| print("debug info") | frappe.logger("mod").info(...) | print() disappears in production |
| frappe.log_error("info msg") | frappe.logger().info(...) | log_error creates Error Log docs, clutters admin UI |
| frappe.logger() (no module) | frappe.logger("my_module") | No-module mixes with framework logs |
| frappe.log_error(title, msg) positional | frappe.log_error(title=t, message=m) | Positional args can swap (known quirk) |
| Log passwords/tokens | Mask sensitive data | SiteContextFilter only masks form_dict |
| frappe.log() in production | frappe.logger() | frappe.log() is debug-only, request-scoped |
| Leave logging=2 in prod | Only during debugging | Logs ALL SQL queries, massive I/O |
| Feature | v14 | v15+ |
|---------|:---:|:----:|
| frappe.logger() | Yes | Yes |
| frappe.log_error() | Yes | + defer_insert kwarg |
| Error Log trace_id | -- | Added |
| Error Log metadata | -- | JSON request/job context |
| Error snapshots | File-based + scheduled collection | Direct DB insert |
| Sentry integration | Basic | Enhanced (DB monitoring, profiling) |
| guess_exception_source() | -- | Identifies which app caused error |
| FRAPPE_STREAM_LOGGING | Yes | Yes |
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
Google Cloud Platform CLI - manage GCP resources including Compute Engine, Cloud Run, GKE, Cloud Functions, Storage, BigQuery, and more.
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.
Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness. Returns a structured report with exact patch locations.
Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.
Take impertio-studio/frappe-core-logging from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.