[core + 4 more] Compute-scoped observability and a per-compute Dashboard - #462
Closed
Simone319 wants to merge 1 commit into
Closed
[core + 4 more] Compute-scoped observability and a per-compute Dashboard#462Simone319 wants to merge 1 commit into
Simone319 wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: 5847dba The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 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
force-pushed
the
zimzha/multi-compute-c4-c7-observability
branch
from
September 2, 2026 11:49
13b0eb8 to
b0660ed
Compare
Base automatically changed from
zimzha/multi-compute-c4-namespace-recording
to
main
September 3, 2026 12:56
Simone319
force-pushed
the
zimzha/multi-compute-c4-c7-observability
branch
from
September 7, 2026 10:40
b0660ed to
bfa0c96
Compare
…ashboard
Move the observability surface onto the compute. Compute gains
enableLogging(retention?) / enableTracing() — public entry points that
flip private loggerEnabled/tracerEnabled flags and drive the protected
provisionLogGroup/applyTracing infra hooks — plus dashboardSection(region),
the single public builder returning { label, health, logging?, tracing? }
gated on those flags. Logger and Tracer now delegate to their resolved
compute instead of touching the Lambda directly. Omitting the Logger's
retention keeps today's behavior: logging is marked enabled (the section
renders) but no LogGroup is provisioned — Lambda's auto-created group
applies (logs never expire).
Dashboard is organized by compute: it takes computes?: Compute | Compute[]
(defaulting to the app's default compute) and renders one group per
compute, with logs/traces appearing automatically for computes that have
a Logger/Tracer attached. The logger/tracer options are removed
(BREAKING). Metrics stay app-scoped and move to
metrics?: MetricsSource | MetricsSource[], pairing each Metrics BB with
its own metricConfigs so widget names stay namespace-correct.
LambdaCompute: buildLambdaWidgets renamed to buildHealthWidgets; widget
builders are protected and guard-throw when the corresponding
observability BB is not attached.
This was referenced Sep 7, 2026
Contributor
Author
|
Superseded by a stacked split for easier review (same change, rebased onto latest
Closing in favor of the stack. |
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.
Problem
Observability Building Blocks (Logger, Tracer, Dashboard) touched the stack's single Lambda handler directly. For multi-compute, observability must attach to the compute that owns it, and the Dashboard must be able to render more than one compute.
Changes
enableLogging(retention?)/enableTracing()public entry points that flip privateloggerEnabled/tracerEnabledflags and drive protectedprovisionLogGroup/applyTracinghooks; single publicdashboardSection(region)returning{ label, health, logging?, tracing? }, gated on those flags.computes?: Compute | Compute[](defaults to the app's default compute); logs/traces sections appear automatically for computes with a Logger/Tracer attached.logger/traceroptions removed (BREAKING); metrics move tometrics?: MetricsSource | MetricsSource[], pairing each Metrics BB with its ownmetricConfigs.buildLambdaWidgets→buildHealthWidgets; widget builders are protected and guard-throw when the corresponding observability BB is not attached.Validation
Checklist
compute-observability-methods.md; DESIGN/README updates)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.