frappe-core-logging

Standardize Frappe logging by using module-scoped frappe.logger('module_name') for routine logs and frappe.log_error for exceptions. This replaces inconsistent print statements and ensures per-module files, structured metadata, and trace context for reliable observability across deployments.

Integrate Sentry with Frappe by combining frappe.log_error for centralized error reporting with optional Sentry integration for production monitoring. This captures traces and structured error metadata, extending visibility beyond default Frappe logs into third-party error tracking dashboards.

Yes, frappe.logger supports production monitoring across Frappe v14 through v16. It provides module-level logging with per-module log files and richer context, ensuring consistent observability without relying on unsafe print statements in live deployment environments.

Using print() in production Frappe apps causes weak error reporting because it bypasses structured logging, lacks trace context, and risks leaking sensitive data. Replacing print() with frappe.logger and frappe.log_error ensures centralized, safe, and observable error metadata capture.

Yes, standardized Frappe logging supports data masking to prevent leaking sensitive data in production. By applying clear requirements for module-scoped logs and structured error metadata, the system ensures safe observability while handling trace context securely across deployments.