frappe-core-logging

To log errors in Frappe for admin visibility, use frappe.log_error() with keyword arguments. This persists exceptions into the Error Log DocType, allowing administrators to review and query production issues directly from the Desk UI.

Frappe logging requires creating module-named loggers using frappe.logger(). This generates rotating log files under sites/{site}/logs/, ensuring traceable operational visibility by separating logs by module name.

Enable HTTP request logging and per-request metrics in Frappe by setting enable_frappe_logger and monitor flags to true in site_config.json. This captures production request data for performance monitoring.

Yes, you can capture unhandled exceptions in Frappe via Sentry by setting the FRAPPE_SENTRY_DSN environment variable. Optional environment variables also enable profiling and database monitoring.

Using positional arguments in frappe.log_error() can swap fields and corrupt error tracking data. You should use keyword arguments instead to ensure exceptions persist correctly into the Error Log DocType.

When implementing Frappe logging, avoid print() usage and ensure secure handling to prevent leaking sensitive tokens or passwords into logs. Use module-named loggers and appropriate site_config.json flags like disable_error_snapshot.