Repository navigation
E2E workflow: CloudWatch through the Lambda into a fresh source - #14
Merged
Merged
Conversation
Pull requests and pushes to main build the ZIP from the checkout and deploy it into a throwaway AWS account with the runtime, architecture and environment variables the docs article names; the daily schedule deploys the released ZIP the docs link to. A fresh log group is subscribed to the Lambda the way the docs describe, 20 lines are written, and every stored row is compared with its CloudWatch event through the team's SQL API connection. Everything is deleted afterwards, plus leftovers older than two hours. AWS access is OIDC through the role in e2e/bootstrap.yaml. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
PetrHeinz
marked this pull request as ready for review
October 15, 2026 17:02
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This workflow only ever assigns Petr, so the assignee input, the Pawel and Collectors secrets and the branch choosing between them go. The issue lands in the Telemetry team, state Plan, project Ingestion for everything, priority High, assigned to Petr. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The bootstrap stack is deployed once per account and already exists, so the template does not need to live in this repository; the header still names the standing e2e-bootstrap stack. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
A new
E2Eworkflow runs the CloudWatch → Lambda → Better Stack setup from the docs in a throwaway AWS account. Pull requests and pushes to main build the ZIP from the checkout withnpm run buildand deploy that, so a change is tested before it is released; the daily schedule deploys the released ZIP the docs link to, which is what customers download.What a run does:
Node.js 22.x→nodejs22.x), architecture and environment variable names from it, failing when the article changes in a way this test does not followaws_cloudwatchsource in the E2E testing team, warms it up until the ingesters accept its token, creates the Lambda with the documented settings, and subscribes a fresh log group to it the way the docs describe[ERROR]prefix, and reads them back through the team's SQL API connection: 20 rows, 5errorand 15info, and every row compared field by field with its CloudWatch event (message with the prefix stripped, level, event timestamp asdt, and the exact context the parser builds: owner, log group, log stream, log id, Lambda name and ARN)The job summary names the release tag or commit that ran and the bundled
@logtail/nodeversion.The account is
better-stack-e2e-lambda(352333568934), a member of the Better Stack organization that holds nothing else. AWS access is GitHub OIDC through thegithub-actions-e2erole of a one-time stack that is already deployed in the account, together with thee2e-lambda-execexecution role. No AWS keys live in GitHub. Pull requests from forks are skipped, since they get no OIDC token.Secrets
TEST_TEAM_TELEMETRY_API,TEST_TEAM_CONNECTION_USERNAMEandTEST_TEAM_CONNECTION_PASSWORDare set. TheLINEAR_*secrets are set as well: a failure on main or on the schedule opens a High-priority issue in the Telemetry team's Plan state, in the Ingestion for everything project, assigned to Petr.🤖 Generated with Claude Code