Curious about what OpenTelemetry is? Check out our website for an explanation!
好奇什么是OpenTelemetry？查看我们的网站获取解释！
The OpenTelemetry specification describes the cross-language requirements and expectations for all OpenTelemetry implementations. Substantive changes to the specification must be proposed using the OpenTelemetry Enhancement Proposal process. Small changes, such as clarifications, wording changes, spelling/grammar corrections, etc. can be made directly via pull requests.
OpenTelemetry 规范描述了所有 OpenTelemetry 实现的跨语言要求和期望。必须使用 OpenTelemetry Enhancement Proposal 流程提出对规范的实质性更改。小的更改，例如澄清、措辞更改、拼写/语法更正等，可以直接通过 pull requests 进行。
Questions that needs additional attention can be brought to the regular specifications meeting. EU and US timezone friendly meeting is held every Tuesday at 8 AM pacific time. Meeting notes are held in the google doc. APAC timezone friendly meeting is held Tuesdays, 4PM pacific time. See OpenTelemetry calendar.
需要额外注意的问题可以提交给定期的 规格会议。欧盟和美国时区友好会议于太平洋时间每周二上午 8 点举行。会议记录保存在 google 文档中。亚太时区友好会议于太平洋时间每周二下午 4 点举行。请参阅 OpenTelemetry 日历。。
Escalations to technical committee may be made over the e-mail. Technical committee holds regular meetings, notes are held here.
可以通过电子邮件向技术委员会上报。技术委员会定期召开会议，记录在这里。
- Overview 总览
- Glossary 词汇表
- Versioning and stability for OpenTelemetry clients OpenTelemetry 客户端的版本控制和稳定性
- Library Guidelines 库准则
- API Specification API规范
- SDK Specification SDK规范
- Data Specification 数据规范
- About the Project 关于工程
The current project status as well as information on notable past releases is found at the OpenTelemetry project page.
Information about current work and future development plans is found at the specification development milestones.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in the specification are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
An implementation of the specification is not compliant if it fails to satisfy one or more of the "MUST", "MUST NOT", "REQUIRED", "SHALL", or "SHALL NOT" requirements defined in the specification. Conversely, an implementation of the specification is compliant if it satisfies all the "MUST", "MUST NOT", "REQUIRED", "SHALL", and "SHALL NOT" requirements defined in the specification.
Changes to the specification are versioned according to Semantic Versioning 2.0 and described in CHANGELOG.md. Layout changes are not versioned. Specific implementations of the specification should specify which version they implement.
Changes to the change process itself are not currently versioned but may be independently versioned in the future.
The official acronym used by the OpenTelemetry project is "OTel".
Please refrain from using "OT" in order to avoid confusion with the now deprecated "OpenTracing" project.
See CONTRIBUTING.md for details on contribution process.
By contributing to OpenTelemetry Specification repository, you agree that your contributions will be licensed under its Apache 2.0 License.