Skip to content

[Observability] Logging: amber engine control-plane lifecycle/error logs #5328

Closed as not planned

Description

@Ma77Ball

Part of #4070.

Goal

Add human-readable lifecycle/error logging across the amber engine control plane.

Problem

The engine control plane (controller, worker lifecycle, scheduling, recovery/replay, client, network setup) emitted little to no log output, making it hard to follow a workflow's execution or diagnose failures.

Scope

  • INFO/DEBUG/WARN/ERROR logging at control-plane boundaries via the AmberLogging trait.
  • No per-tuple/per-message logging on the data hot path.
  • Non-functional; no behavior change.

Branch: chore/logging-amber-engine

Activity

  1. Ma77Ball commented on Jun 3, 2026

    @Ma77Ball
    ContributorAuthor

    /parent-issue #4070

  2. Ma77Ball commented on Jun 3, 2026

    @Ma77Ball
    ContributorAuthor

    /take

  3. Ma77Ball commented on Jun 3, 2026

    @Ma77Ball
    ContributorAuthor

    Closing for now — consolidating the approach/procedure into discussion #5355 for feedback before raising PRs. Will reopen as PRs land.

  4. Ma77Ball commented on Jun 4, 2026

    @Ma77Ball
    ContributorAuthor

    /unparent-issue #4070

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions