Token导航 LogoToken导航TokenDH.com
开发敏感数据github未标认证来源可访问许可证需确认审计通过

frappe-core-logging冰沙岩心测井

Agent Skill

frappe-core-logging 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 Codex、Claude、Cursor、Gemini CLI 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

624

周安装

25

GitHub Stars

87

下载量

202
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:frappe-core-logging(冰沙岩心测井)
来源仓库:https://github.com/openaec-foundation/erpnext_anthropic_claude_development_skill_package
仓库路径:skills/frappe-core-logging
安装命令:
npx skills add https://github.com/openaec-foundation/erpnext_anthropic_claude_development_skill_package --skill frappe-core-logging
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/openaec-foundation/erpnext_anthropic_claude_development_skill_package --skill frappe-core-logging

简介

用于记录任务执行中的错误、用户纠正和经验缺口。frappe-core-logging 属于开发类 Skill,可作为该场景下的辅助能力补充。

  • 适合让 Agent 持续沉淀问题和修正最佳实践。
  • 可结合来源仓库和原始 README 核验具体用法。
  • 安装前建议确认权限范围和维护状态,避免触发不必要操作。
  • 注意是否会触发联网、命令执行或文件读写,确保安全使用。

SKILL.md

Frappe Logging & Error Tracking

Three Logging Mechanisms

MechanismStorageUse 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-scopedQuick debugging only (NOT for production)

Decision Tree

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

Quick Reference: frappe.logger()

# 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)

Default Log Levels

ModeLevelEffect
Development (_dev_server)WARNINGDebug/info suppressed
ProductionERROROnly errors and above
# Change level dynamically
frappe.utils.logger.set_log_level("DEBUG")

Quick Reference: frappe.log_error()

# 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()

Auto-Captured Exceptions

Unhandled exceptions (HTTP 500+) are automatically logged to Error Log.

Excluded from auto-capture:

  • frappe.AuthenticationError
  • frappe.CSRFTokenError
  • frappe.SecurityException
  • frappe.InReadOnlyMode

Production Configuration

site_config.json Keys

KeyValueEffect
enable_frappe_loggertrueHTTP request logging → frappe.web.log
logging2Log all SQL queries (debug only!)
monitortrueRequest/job metrics → monitor.json.log
disable_error_snapshottrueDisable auto-capture of exceptions

Environment Variables

VariableEffect
FRAPPE_STREAM_LOGGING=1Log to stderr instead of files
FRAPPE_SENTRY_DSN=<dsn>Enable Sentry error tracking
ENABLE_SENTRY_DB_MONITORINGTrack SQL queries in Sentry
SENTRY_TRACING_SAMPLE_RATEPerformance tracing rate (0.0-1.0)

Production Log Files

FileContent
logs/web.error.logHTTP errors (supervisor)
logs/web.logGunicorn stdout
logs/worker.error.logBackground job errors
logs/frappe.logDefault frappe logger
logs/frappe.web.logHTTP request metadata
logs/monitor.json.logPerformance metrics (JSON)
sites/{site}/logs/*.logPer-site application logs

Anti-Patterns

NEVERALWAYSWhy
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) positionalfrappe.log_error(title=t, message=m)Positional args can swap (known quirk)
Log passwords/tokensMask sensitive dataSiteContextFilter only masks form_dict
frappe.log() in productionfrappe.logger()frappe.log() is debug-only, request-scoped
Leave logging=2 in prodOnly during debuggingLogs ALL SQL queries, massive I/O

Version Differences

Featurev14v15+
frappe.logger()YesYes
frappe.log_error()Yes+ defer_insert kwarg
Error Log trace_id--Added
Error Log metadata--JSON request/job context
Error snapshotsFile-based + scheduled collectionDirect DB insert
Sentry integrationBasicEnhanced (DB monitoring, profiling)
guess_exception_source()--Identifies which app caused error
FRAPPE_STREAM_LOGGINGYesYes

Reference Files

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.66%
按下载量换算70

Claude

28.31%
按下载量换算57

Cursor

19.27%
按下载量换算39

Gemini CLI

8.6%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills