[core + 3 more] Route logging retention and tracing through the compute - #504
Closed
Simone319 wants to merge 1 commit into
Closed
[core + 3 more] Route logging retention and tracing through the compute#504Simone319 wants to merge 1 commit into
Simone319 wants to merge 1 commit into
Conversation
Move retention and X-Ray ownership from bb-logger/bb-tracer into the Compute abstraction: enableLogging(retentionDays?) sets retention on the compute's own log group (last-wins + synth conflict warning), and enableTracing() turns on active X-Ray + trace-publish permission. Both delegate to protected applyLogRetention/applyTracing hooks implemented by the concrete compute. bb-logger and bb-tracer now call the compute seam instead of reaching into the shared handler's log group / function directly.
🦋 Changeset detectedLatest commit: a24eaea The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Simone319
changed the title
This was referenced Sep 7, 2026
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.
Part 1 of 2 (stacked) — the compute observability seam, split out of #462.
What
Move logging-retention and tracing ownership from the observability Building Blocks into the
Computeabstraction:Compute.enableLogging(retentionDays?)— sets retention on the compute's single log group when a value is given; owns the last-wins + synth conflict-warning policy across multiple Loggers.Compute.enableTracing()— turns on active X-Ray tracing + trace-publish permission on the shared role.applyLogRetention/applyTracingareprotectedabstract hooks implemented byLambdaCompute, so the policy always runs.bb-loggerandbb-tracernow delegate to the resolved compute instead of reaching into the shared handler's log group / function directly.No dashboard changes here — those are in the stacked PR on top.
Stack
mainTest
build,biome check,lint:deps, and unit tests (bb-lambda-compute, bb-logger, bb-tracer, bb-async-job, bb-cron-job, core targeted) pass on Node 22.