Repository navigation
chore: turn on traces, invocation logs and source maps for the landing Worker - #48
Merged
Merged
Conversation
…g Worker Every deploy from the repository replaces the Worker's dashboard settings, so observability lives in wrangler.jsonc: logs with each invocation, traces, both for every request, and source maps for readable stack traces.
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.
Every deploy from the repository replaces the Worker's dashboard settings, so the landing Worker's observability lives in
apps/landing/wrangler.jsonc:head_sampling_rate: 1,invocation_logs)All within the Workers Free plan: 200,000 log events a day, kept 3 days.
wrangler deploy --dry-runaccepts the config with no warnings; the bundle is unchanged (10 KiB).