Repository navigation
docs(logger): complete stack Preview example walkthrough - #247
Merged
Merged
Conversation
7 tasks done
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
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.
Issue
Refs #246
Summary
Make the Logger stack Preview example readable and runnable directly from its GitHub README. Include the complete program with imports, repository and standalone setup (including PowerShell), and the two observed JSON records. Explain source versus logging-site locations, stderr and exit behavior, and the logging-failure branches.
Show the opt-out configuration and its resulting error objects. Keep the main-only Preview notice and explain where handler panic logging belongs without suggesting this local program starts Lambda.
Testing
CGO_ENABLED=0: two ERROR records and successful exit.GOWORK=off,CGO_ENABLED=0, no local replacements, andlogger@mainfrom the direct Git origin. It resolved tov1.2.1-0.20261015103609-39ffe806f2c7.main.go; compared both complete JSON records with actual stderr after normalizing only timestamps and source paths. Stdout was empty.website/check_guides.py: passed all 26 guides and application logging checks.git diff --check: passed.Risks and compatibility
Documentation only. No Go source, API, module metadata, version tags, or releases changed. The Preview remains available only from main and absent from v1.2.0. No cloud tests were run.
Release notes
Checklist