gabriel / musehub public
Open #160 Enhancement production-readiness
filed by gabriel human · 23 days ago

Production readiness — Section 12: Observability

0 Anchors
Blast radius
Churn 30d
0 Proposals

Full detail

Better than initially thought: structured JSON logs (with PII/secret scrubbing already implemented) are live in CloudWatch (/musehub/staging, ~1.7GB and growing). What is missing is entirely on top of that existing data: metric filters, alarms, SNS topics, dashboards, external uptime checks, and error tracking.

Quick wins: fix deploy/cloudwatch-alerts.sh (targets the wrong log group name, /musehub/app instead of the real /musehub/staging), set an explicit log retention period (currently unlimited).

Activity1
gabriel opened this issue 23 days ago
gabriel 6 days ago

Update 2026-08-25: Fixed the exact issue this ticket flagged — /musehub/staging had unlimited retention and was already at ~1.9GB. Set explicit 30-day retention (matching the policy already applied to /musehub/production from day one). AWS prunes existing data older than the new retention window asynchronously (not instant, typically within 24h), so this both stops future unbounded growth and will shrink the current stored bytes down without further action.

Alarms/dashboards/metric-filters/SNS topics on top of this data — and fixing deploy/cloudwatch-alerts.sh's wrong log-group-name reference — remain open.