feat: 10GB worker + DLQ depth alarm#68
Merged
Merged
Conversation
- worker_lambda_memory: 3008 -> 10240. Lambda allocates vCPU proportional to RAM; ~3x more vCPU should let large packages finish inside the 15-min cap. Per-package cost stays roughly flat. - New CloudWatch alarm on the DLQ. Anything in the DLQ means a worker invocation failed twice (unhandled exception or 15-min timeout). - Tiny notifier Lambda (stdlib only, ~25 LOC) subscribed to a new SNS topic. Forwards alarm events as a Discord embed to the same WH_URL webhook the worker uses for package-processed notifications, so DLQ alerts land in the same channel.
Androz2091
force-pushed
the
feat/bigger-worker-and-dlq-alarm
branch
from
a1a0c1d to
f24c7e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two changes for handling large packages, plus alerts straight to Discord.
WH_URLwebhook the worker uses for package-processed notifications, so DLQ alerts land in the same channel. No email, no AWS Chatbot.