Back to Details

otel-telemetry-emissions

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Telemetry Emissions

遥测数据生成

A registry of what telemetry OpenTelemetry components actually emit, pinned to upstream versions.
Note: The telemetry emissions in these files were detected by LLM analysis of the upstream source and may contain errors. Verify against the component's source or docs before relying on a row for critical decisions.
这是一个记录OpenTelemetry组件实际生成的遥测数据的注册表，与上游版本绑定。
注意： 这些文件中的遥测数据生成信息是通过LLM分析上游源代码检测得到的，可能存在错误。在依据某一行信息做出关键决策前，请对照组件的源代码或文档进行验证。

Layout

目录结构

<repo basename>/<path in repo>/v<version>.md
Example: 
opentelemetry-collector-contrib/receiver/kafkareceiver/v0.158.0.md
One file per scanned version. The files in a component directory are its telemetry history; 
index.md
lists every file — start there to see what is covered.
<repo basename>/<path in repo>/v<version>.md
示例：
opentelemetry-collector-contrib/receiver/kafkareceiver/v0.158.0.md
每个被扫描的版本对应一个文件。组件目录下的文件构成其遥测历史；
index.md
列出所有文件——可从这里开始查看覆盖范围。

Looking up a component at a version

查询特定版本的组件信息

  1. Find the component's directory (or its row in 
    index.md
    ).
  2. Pick the file matching the target version exactly.
  3. If there is no exact match, use the file with the highest version below the target and say the exact version is unverified.
  4. If the component or version is not covered at all, say so — do not infer telemetry from semantic conventions.
  1. 找到组件的目录（或其在
    index.md
    中的对应行）。
  2. 选择与目标版本完全匹配的文件。
  3. 如果没有完全匹配的版本，使用版本号低于目标版本且最高的文件，并注明确切版本未经验证。
  4. 如果组件或版本完全未被覆盖，请如实说明——不要从语义规范推断遥测数据。

What a data file contains

数据文件包含内容

Frontmatter (
repo
, 
path
, 
version
, 
scope_name
, 
commit_sha
, 
last_verified
), then per-signal tables:
  • Traces — span name, kind, attributes, notes
  • Metrics — metric name, instrument type, unit, attributes, notes
  • Logs — log/event name, attributes, notes
scope_name
is the component's instrumentation scope — the anchor for matching runtime telemetry back to the component. Absent signals are omitted entirely. 
Notes
marks conditional emission (feature gates, opt-in config, experimental semconv). 
Sources
lists the upstream files the data came from.
文件包含前置元数据（
repo
、
path
、
version
、
scope_name
、
commit_sha
、
last_verified
），然后是按信号分类的表格：
  • Traces — span名称、类型、属性、备注
  • Metrics — metric名称、工具类型、单位、属性、备注
  • Logs — 日志/事件名称、属性、备注
scope_name
是组件的instrumentation scope——用于将运行时遥测数据与组件匹配的锚点。未涉及的信号会被完全省略。
Notes
标记条件性生成（功能开关、可选配置、实验性semconv）。
Sources
列出数据来源的上游文件。