[saluja-ji]

Fixes #9135
Fixes #9134

Also clarify the behavior of repeated Shutdown calls.

Documentation-only change; no behavior changes.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: saluja-ji / name: saluja-ji (39e052a)

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on the author · refreshed 2026-10-23 20:22 UTC

Respond to 1 review item (e.g. link a commit, explain why not, ask a follow-up):

• Top-level threads: 1

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Should this be with reviewers? Comment /dashboard route:reviewers to route it to them.
• Anything wrong — including the routing? Report it with what you expected; it helps us improve the dashboard.

[Copilot]

🟢 Approval recommended

The documentation matches existing behavior, and no unresolved issues remain.

No open issues 🎉

What changed in this PR

Documents the OTLP/gRPC log exporter’s concurrency contract, addressing #9135 without changing runtime behavior.

Changes:

• Clarifies concurrency guarantees for Export, Shutdown, and ForceFlush, plus repeated shutdown behavior.
• Adds a changelog entry.

File	Description
exporters/​otlp/​otlplog/​otlploggrpc/​exporter.go	Documents concurrency and repeated shutdown guarantees.
CHANGELOG.md	Records the documentation update.

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The documentation matches existing behavior, and no unresolved issues remain.

No open issues 🎉

_{Review effort: Balanced}

[pellared]

Can we also solve #9134 in the same PR?

[saluja-ji]

Can we also solve #9134 in the same PR?

Yes, I will add the same documentation to otlploghttp in this PR. That includes that ForceFlush is a no op, and that Shutdown doesn't wait for or cancel in flight exports. I will update the title and description to cover both issues.

[pellared]

Shouldn't we also add this sentence in exporters/otlp/otlplog/otlploggrpc/exporter.go?

[saluja-ji]

I think the sentence fits HTTP but not gRPC as written. In gRPC, Shutdown acquires clientMu, which Export holds for the duration of the upload, so it waits for in-flight exports (it still doesn't cancel them). I think documenting that distinction in the gRPC Shutdown comment would be more accurate than copying the HTTP wording, but I'm happy to go with whichever you prefer

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.4%. Comparing base (d376be4) to head (bc6eb0e).

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #9244     +/-   ##
=======================================
- Coverage   89.4%   89.4%   -0.1%     
=======================================
  Files        345     345             
  Lines      22687   22687             
=======================================
- Hits       20289   20288      -1     
- Misses      2398    2399      +1     

Files with missing lines	Coverage Δ
exporters/otlp/otlplog/otlploggrpc/exporter.go	92.3% <ø> (ø)
exporters/otlp/otlplog/otlploghttp/exporter.go	95.4% <ø> (ø)

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.