[WIP] Fix Go Logger Enhancement workflow failure#7485
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds additional debug logging around the tracing OTLP fanout span exporter to help diagnose/export/shutdown behavior and backend failures.
Changes:
- Log when
newFanoutExporterbypasses fanout (single exporter) vs creates a fanout exporter. - Log fanout export start, per-backend export errors, and a failure summary.
- Log fanout shutdown start, per-backend shutdown errors, and completion status.
Show a summary per file
| File | Description |
|---|---|
| internal/tracing/fanout.go | Adds debug logging around fanout exporter creation, span export, and shutdown flows. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 2
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
@copilot resolve the merge conflicts in this pull request |
Adapt debug logging to the refactored forEachExporter helper introduced in main (Refactor fanout exporter concurrent dispatch #7486). The op string parameter to forEachExporter carries operation context into per-backend error log messages, satisfying the reviewer request to identify which exporter failed.
Resolved in commit 61c8af0. The conflict arose because main refactored the concurrent dispatch logic into a new |
internal/tracing/fanout.gousing the existinglogTracingpackage-level loggermake agent-finished