docs-cn
docs-cn copied to clipboard
open-telemetry
OpenTelemetry 中文文档: 接入使用、技术标准、RFC、SDK等.
新增文件夹 community/opentelemetryGoInstrumentation 存放go的Instrumentation的文档 原文地址：https://opentelemetry.io/docs/instrumentation/go/ - [ ] index.md https://github.com/open-telemetry/docs-cn/pull/117 - [ ] getting-started.md https://github.com/open-telemetry/docs-cn/pull/114 - [ ] libraries.md https://github.com/open-telemetry/docs-cn/pull/116 - [ ] manual.md https://github.com/open-telemetry/docs-cn/pull/115 - [ ] exporting_data.md https://github.com/open-telemetry/docs-cn/pull/113
原文地址：https://opentelemetry.io/docs/reference/specification/logs/overview/ 原文档仓库地址：https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/logs 翻译输出文件夹：https://github.com/open-telemetry/docs-cn/tree/main/specification/logs - [ ] [README.md](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/README.md) - [ ] [data-model.md](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md) - [ ] [logging-library-sdk.md](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/logging-library-sdk.md) - [ ] [semantic_conventions](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/logs/semantic_conventions)
### 项目结构的定义 ``` ├── COMMUNITY-CN.md ├── CONTRIBUTING-CN.md ├── README.md ├── community ├── libs │ └── java ├── original │ ├── community # https://github.com/open-telemetry/community │ ├── specification # https://github.com/open-telemetry/opentelemetry-specification │ └──...
telemetry，有时候翻译成遥测，有时候翻译成遥感 trace，是用追踪还是链路，还是直接用英文原文 类似的应该还有很多，我觉得我们需要统一下规范，避免读者阅读时的困惑甚至翻译时的困惑。
我个人比较赞成这种方式 > 中文正文及标题中出现的英文及数字应该使用半角方式输入，并且在左右各留一个半角空格。如果这些这些半角英文及数字的左边或者右边紧接着任何的中文全角括号或者其他标点符号的话，则不需要加入半角空格。
Signed-off-by: rogerogers chore: trace api fix link and some translate
