This repository has been archived on 2026-08-04. You can view files and clone it, but cannot push or open issues or pull requests.

Adam Moussa e5f68f1cd3 feat(exec-aide): CloudWatch alarm coverage for Lambdas, DynamoDB, ECS ... Add ALARM-only CloudWatch alarms routed to the shared site-alerts SNS topic (imported once via Topic.fromTopicArn and injected into both constructs via props). All alarms use treatMissingData NOT_BREACHING and have no OK / InsufficientData actions, mirroring the proposal-system alarm construct. Lambda (fetch-classify, daily-digest, conversation): - Errors (Sum >= 1, eval 1) - Throttles (Sum >= 1, eval 1) - Duration (p99, eval 3 / datapoints 2, ~80% of timeout: 96000ms for the 120s fns, 144000ms for conversation's 180s) -- thresholds pending Adam sign-off. DynamoDB exec-aide table: - ThrottledRequests and SystemErrors. These metrics are NOT published at the bare TableName dimension (CDK's metricThrottledRequests / metricSystemErrors are deprecated as invalid); they are keyed by the Operation dimension. Used the *ForOperations math helpers scoped to the 6 operations this single-table app issues (GetItem/PutItem/Query/Scan/ UpdateItem/DeleteItem) to stay within the 10-metric math-expr cap. ECS exec-aide-listener Fargate service (AWS/ECS, no Container Insights): - CPU and Memory utilization (Average > 80%, eval 3 / datapoints 2). - Service assigned to a const (logical id 'Service' unchanged) so metrics can reference it. The RunningTaskCount alarm (requires Container Insights) is intentionally deferred to a separate sign-off-gated commit.		2026-06-17 13:56:25 -04:00
..
email-pipeline.ts	feat(exec-aide): CloudWatch alarm coverage for Lambdas, DynamoDB, ECS	2026-06-17 13:56:25 -04:00
socket-mode.ts	feat(exec-aide): CloudWatch alarm coverage for Lambdas, DynamoDB, ECS	2026-06-17 13:56:25 -04:00