home/writing/prod-log-monitor

Prod Log Monitor

GPTClaudeGemini··▲ 1,251 copies·updated 2026-07-14

prod-log-monitor.prompt

<!-- vcp-version: v0.9.5 -->
<!-- methodology-version: v1.4 -->
<!-- vcp-version: v0.8.4 -->

<!-- vcp-version: v0.8.2 -->

<!-- vcp-artifact: PROD_LOG_MONITOR_PROMPT -->
<!-- vcp-version: v0.8.2 -->

Read the project-specific operations docs first.
Discover the canonical authorized production log command or log path before doing anything else.
Use a bounded recent window, default 30 minutes unless the project documents another window.
Capture real errors only.
Ignore access-log noise and healthy events.
Redact secrets, tokens, cookies, authorization headers, and personal data.
Write safe inbox entries under `.vcp/runtime/error-inbox/`.
Produce a short capture report with count and file paths.
Do not fix, do not root-cause, do not deploy, do not change configuration, and do not commit runtime files.

when to use it

Community prompt sourced from the open-source GitHub repo Gudvin82/vibe-coding-protocols (NOASSERTION). A "Prod Log Monitor" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.