Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

docs: clarify unit for OTEL_EXPORTER_OTLP_TIMEOUT default#4860

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
ta-ke-inf wants to merge3 commits intoopen-telemetry:main
base:main
Choose a base branch
Loading
fromta-ke-inf:feature

Conversation

@ta-ke-inf
Copy link

@ta-ke-infta-ke-inf commentedDec 17, 2025
edited
Loading

Description

Clarify the unit for the documented default value ofOTEL_EXPORTER_OTLP_TIMEOUT in the SDK environment variables docs.

The current docs showDefault: 10 without stating the unit, which can lead to operators misinterpreting the value (e.g., 10ms vs 10s). This PR updates only the default line to make the unit explicit while keeping the surrounding wording consistent with existing env var docs.

Fixes#4858

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Built the docs locally with Sphinx

Repro steps:

  • python -m pip install -r docs-requirements.txt
  • cd docs && python -m sphinx -b html -D master_doc=sdk/environment_variables . _build/html_envvars

Does This PR Require a Contrib Repo Change?

  • Yes. - Link to PR:
  • No.

Checklist:

  • Followed the style guidelines of this project
  • Changelogs have been updated (not needed for docs-only clarification)
  • Unit tests have been added (not applicable)
  • Documentation has been updated

chatgpt-codex-connector[bot] and p-x9 reacted with thumbs up emoji
@ta-ke-infta-ke-inf requested a review froma team as acode ownerDecember 17, 2025 05:10
@linux-foundation-easycla
Copy link

linux-foundation-easyclabot commentedDec 17, 2025
edited
Loading

CLA Signed

The committers listed above are authorized under a signed CLA.

@xrmxxrmx moved this toEasy to review / merge / close in@xrmx's Python PR digestDec 17, 2025
Copy link
Member

@emdnetoemdneto left a comment

Choose a reason for hiding this comment

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

This reminded me that we need to update matrix compliance#4044 (comment)

I think it is worth having a quick note on this env var stating it is not compliant and referring to#4044.

ta-ke-inf reacted with heart emoji
…__init__.pyCo-authored-by: Emídio Neto <9735060+emdneto@users.noreply.github.com>
@ta-ke-inf
Copy link
Author

@emdneto

a2a2ddf

Thank you! As also mentioned in#4044, it seems thatOTEL_EXPORTER_OTLP_TIMEOUT currently needs to be specified in milliseconds, so to avoid confusion I propose updating the documentation to use10000 instead of10 for now.

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

Reviewers

@emdnetoemdnetoAwaiting requested review from emdneto

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

Status: Easy to review / merge / close

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Docs: clarify unit for OTEL_EXPORTER_OTLP_TIMEOUT (seconds vs milliseconds)

2 participants

@ta-ke-inf@emdneto

[8]ページ先頭

©2009-2025 Movatter.jp