dohertj2/ScadaBridge
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases Wiki Activity

Capture other actors' log lines per execution (ExecutionId log enrichment) #56

New Issue
Open
opened 2026-11-06 15:24:39 -05:00 by dohertj2 · 0 comments
dohertj2 commented 2026-11-06 15:24:39 -05:00
Owner
Copy Link
Copy Source

Register row 115 (deferred-work register).

Flow Debugger step logs capture the script's own Log.* and runtime lines inside scoped helpers only. Instance Actor, DCL, alarm actors and S&F log lines never reach the graph: no LogContext.PushProperty calls, Enrich.FromLogContext() not configured, and site_events has no execution-id column. Proposed: push ExecutionId (+ instance/script) onto LogContext at run start, enable Enrich.FromLogContext(), add an execution-id column + index to site_events (replicated table → both-nodes-together schema change), then sink or query by execution id.

Revisit trigger (from register): First investigation where the answer is in Instance Actor/DCL logs of a traced run that the operator cannot correlate by hand.

Current state: Out of scope for step logs; not started.
Related: docs/plans/2026-09-09-flow-debugger-step-logs-design.md §2, §9.

Source: docs/plans/2026-07-08-deferred-work-register.md row 115

Register row 115 (deferred-work register). Flow Debugger step logs capture the script's own `Log.*` and runtime lines inside scoped helpers only. Instance Actor, DCL, alarm actors and S&F log lines never reach the graph: no `LogContext.PushProperty` calls, `Enrich.FromLogContext()` not configured, and `site_events` has no execution-id column. Proposed: push `ExecutionId` (+ instance/script) onto `LogContext` at run start, enable `Enrich.FromLogContext()`, add an execution-id column + index to `site_events` (replicated table → both-nodes-together schema change), then sink or query by execution id. **Revisit trigger (from register):** First investigation where the answer is in Instance Actor/DCL logs of a traced run that the operator cannot correlate by hand. **Current state:** Out of scope for step logs; not started. Related: `docs/plans/2026-09-09-flow-debugger-step-logs-design.md` §2, §9. Source: `docs/plans/2026-07-08-deferred-work-register.md` row 115
dohertj2 added the type:featurepriority:p3migrated labels 2026-11-06 15:24:39 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked
Blocked by dependency or external hold
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label migrated priority:p3 type:feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/ScadaBridge#56
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?