Skip to content

chore(logging): correct wide-event comments, document the sink split - #1016

Open
alexluong wants to merge 2 commits into
mainfrom
chore/logging-wide-event-comments
Open

chore(logging): correct wide-event comments, document the sink split#1016
alexluong wants to merge 2 commits into
mainfrom
chore/logging-wide-event-comments

Conversation

@alexluong

Copy link
Copy Markdown
Collaborator

delivery.attempted and event.received are emitted with Info, but the comments around them called them audit events. That wording is left over from the multi-line Audit() calls they replaced in #913 — the same commit introduced both the wide events and the Audit→OTel split, and deliberately put per-unit-of-work lines on the operator sink. Nothing routes them to the OTel logs SDK, so the comments described behavior that doesn't exist.

  • logging.Logger — say which sink a line belongs on, once, next to the split it describes
  • messagehandler.go, eventhandler.go — drop the "replaces X and Y" history and the re-explanation of the wide-event pattern; keep only what the code can't say (why retryOutcome exists, why swallowing an attempt error is safe)

Comments only; no behavior change.

🤖 Generated with Claude Code

alexluong and others added 2 commits August 4, 2026 15:49
The hot-path wide events (delivery.attempted, event.received) are Info, but
several comments around them called them audit events — leftover wording from
the multi-line audit calls they replaced. Nothing routes them to the OTel logs
sink, so the comments described behavior that doesn't exist.

Say where each sink's line belongs once, on logging.Logger, and drop the
history and re-explanation from the call sites.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The struct doc's job is the type — two sinks, what each is. Which method a
call site should pick is doc for Audit, and doesn't need a list of call sites
that goes stale.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant