# 07_naive_incomplete#1 — FAILED | field | value | |---|---| | campaign | RERUN (mongodb × aws) | | archetype | generative | | date | 2026-10-30T12:20Z | | gate version | v1 | | deployment | dep-c7fe5e88 | | deploy status | healthy (930s) | | gate | healthz=✓ connection=✓ logs=✗ metrics=✓ | | teardown clean | True | ## Attribution - **bucket:** AGENT - **class:** cloudwatch-agent-ctl-path - **evidence:** Health, the authenticated write and metrics were green; the mongod log group existed with zero entries. The render installed the CloudWatch agent from the Ubuntu package and then started it with the control path that exists only on Amazon Linux images with the agent preinstalled; the package ships it under /opt/aws/amazon-cloudwatch-agent/bin. The fail-soft log-shipping stage swallowed 'No such file', so the agent never ran and the product's Logs view would have stayed blank on a healthy, writable database. The same scenario's 26 Oct render used the right path and shipped logs. - **resolution:** Fixed (dc557a2b, 4edb62cb): a plan-stage rule refuses a VM script that installs the agent from a package and starts it with the preinstalled-image path; a script with no package install is not judged. Re-run after the rule went live: see row 07_naive_incomplete#2. ## Recorded reason (scrubbed) ``` gate failed: {"logs": "log groups exist but carry no entries: ['/mongodb/mongo-6d89j9/mongod']"} ```