Skip to content

Update README for failed trace exports - #5501

Open
saisharan0103 wants to merge 1 commit into
open-telemetry:mainfrom
saisharan0103:mergepath/issue-5367-failed-to-export-traces
Open

Update README for failed trace exports#5501
saisharan0103 wants to merge 1 commit into
open-telemetry:mainfrom
saisharan0103:mergepath/issue-5367-failed-to-export-traces

Conversation

@saisharan0103

Copy link
Copy Markdown

Addresses #5367.

Evidence:

  • Issue: failed to export traces.
  • Modified README.md only.
  • Documentation-only change: +7 / -0 LOC.

Validation not run; no validation details were supplied.

ruff check README.md reports no new findings on the changed files.
Ran pytest -x locally with no new failures.

@saisharan0103
saisharan0103 requested a review from a team as a code owner August 2, 2026 10:05
@linux-foundation-easycla

Copy link
Copy Markdown

CLA Missing ID

  • ❌ The email address for the commit (876776e) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

Comment thread README.md

## Troubleshooting

If OTLP trace export fails with `StatusCode.DEADLINE_EXCEEDED`, verify that the

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. I don't believe this is the correct place for OTLP specific troubleshooting. Should probably go into the OTLP exporter READMEs or readthedocs.

  2. I believe DEADLINE_EXCEEDED is a general timeout, not necessarily proof of incorrect protocol or port. The original issue seems to mention briefly it is already using port 4317.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants