[bb-dashboard + 3 more] Organize the Dashboard by compute (finalize-deferred) - #505
Closed
Simone319 wants to merge 1 commit into
Closed
Conversation
🦋 Changeset detectedLatest commit: d4971fd 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
3 tasks
Compute gains dashboardSection(region) + presence flags (loggerEnabled/ tracerEnabled) + protected healthWidgets/loggingWidgets/tracingWidgets abstracts; LambdaCompute implements them. The Dashboard renders a compute-scoped section (health always; logs/traces when a Logger/Tracer is attached) instead of taking logger/tracer options. Metrics stay app-scoped via MetricsSource. MetricsSource is re-exported from @aws-blocks/blocks; LoggerBBRef/TracerBBRef deprecated. The Dashboard builds its widget body via a Dashboard-specific core seam (registerDashboardFinalizer / finalizeDashboards, run at the end of create()) rather than in its constructor, so it observes every Logger/Tracer regardless of construction order. Kept Dashboard-specific (not a generic finalizer registry) since it is the only deferred-build case today.
Simone319
force-pushed
the
zimzha/compute-observability-dashboard
branch
from
September 7, 2026 16:39
ee5da28 to
d4971fd
Compare
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 2 of 2 — the per-compute Dashboard, stacked on #504. Split out of #462.
What
Compute.dashboardSection(region)+ presence flags (loggerEnabled/tracerEnabled) +protectedhealthWidgets/loggingWidgets/tracingWidgetsabstracts;LambdaComputeimplements them.logger/traceroptions. Metrics stay app-scoped viaMetricsSource(now re-exported from@aws-blocks/blocks).LoggerBBRef/TracerBBRefare@deprecated.registerFinalizer/runFinalizerscore seam, run at the end ofBlocksStack/BlocksBackend.create(). The Dashboard builds its widget body in a finalizer so it observes every Logger/Tracer regardless of construction order — a Dashboard created before its Loggers still renders their sections.Breaking (Dashboard)
logger/traceroptions removed (attaching the BB is the signal);metricConfigsmoves inside the metrics source. Migration is in the changeset.Stack
mainzimzha/compute-observability-logging-tracing(auto-retargets tomainwhen [core + 3 more] Route logging retention and tracing through the compute #504 merges)Test
build,biome check,lint:deps,check:api, and unit tests (bb-dashboard incl. a Dashboard-before-Logger order-independence synth test, bb-lambda-compute, core targeted) pass on Node 22.