Site: one wide event per request for email and release routes - #4
Merged
Merged
Conversation
Each request now emits a single structured event with deployment context and why it ended (bot check, gate, validation, missing settings, SES error type), to Axiom and the function log with the ingest result. No address, IP, header, body or error message is ever recorded.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Adds
apps/site/lib/log: one structured wide event per request (canonical log line) with deployment context (commit, deployment, environment, region), request id, status, outcome and duration, sent to Axiom and written to the function log with the ingest result.The email route records why a request ended: bot check result, which gate rejected it, the validation verdict, missing settings by name, and the SES/STS error type and HTTP status. That answers today's "Email is unavailable" 503, which left no trace. The release routes move onto the same event. Nothing records an email address, its domain, an IP, headers, the body or an error message; tests assert it.
Site tests (187), typecheck, lint, production build and the fake-only feed smoke pass.