⚙️ Infrastructure: Persistent Logging to PostgreSQL

[BillChirico]

Add a PostgreSQL transport to Winston so bot logs are persisted to the database alongside file/console output.

Requirements

• Custom Winston transport that writes log entries to a PostgreSQL table
• Log table schema: id, level, message, metadata (JSONB), timestamp
• Configurable via config.json (enable/disable, min log level for DB, retention days)
• Auto-prune old logs based on retention config
• Query endpoint or utility for viewing logs (for future dashboard integration)
• Should not block or slow down the bot if DB is unavailable — fail gracefully
• Respect existing log levels and structured metadata already in use

Implementation Notes

• Use the existing db.js pool — no separate connection
• Migration: CREATE TABLE IF NOT EXISTS on startup
• Consider batch inserts to reduce DB round-trips
• Index on timestamp + level for efficient querying
• Dashboard task will eventually consume these logs

Acceptance Criteria

• Logs written to PostgreSQL
• Configurable retention and pruning
• No performance impact when DB unavailable

[coderabbitai]

🔗 Related PRs

#4 - Structured Logging System [merged]
#14 - feat: PostgreSQL-backed config persistence [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[michaellinhq]

Hi, I reviewed '⚙️ Infrastructure: Persistent Logging to PostgreSQL' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.