You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Activity
Ma77Ball commentedon Jun 3, 2026
/parent-issue #4070
Ma77Ball commentedon Jun 3, 2026
/take
Ma77Ball commentedon Jun 3, 2026
Closing for now — consolidating the approach/procedure into discussion #5355 for feedback before raising PRs. Will reopen as PRs land.
Ma77Ball commentedon Jun 4, 2026
/unparent-issue #4070