Skip to content

Commit 846241f

Browse files
Add metadata notes (#351)
1 parent 2dced02 commit 846241f

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

docs/reference/edot-collector/config/default-config-k8s.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,12 @@ The [`filelog`] and [`hostmetrics`] receivers are used to gather container logs
4444

4545
Logs and metrics are batched for better performance ([`batch`] processor) and then enriched with meta information using the [`k8sattributes`], [`resourcedetection`] and [`resource`] processors.
4646

47+
:::{note}
48+
The `from_context: client_metadata` option in the `resource` processor only applies to transport-level metadata. It cannot extract custom application attributes.
49+
50+
To propagate such values into your telemetry, set them explicitly in your application code using EDOT SDK instrumentation. For more information, refer to [EDOT Collector doesn’t propagate client metadata](docs-content://troubleshoot/ingest/opentelemetry/edot-collector/metadata.md).
51+
:::
52+
4753
### Application telemetry through OTLP from OTel SDKs
4854

4955
The Daemonset collectors also receive the application telemetry from OTel SDKs that instrument services and pods running on corresponding Kubernetes nodes.

docs/reference/edot-collector/config/default-config-standalone.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,12 @@ The goal of EDOT is to preserve OTel data formats and semantics as much as possi
5353

5454
For logs collection, the default configuration uses the [`filelog`] receiver to read log entries from files. In addition, the [`resourcedetection`] processor enriches the log entries with metadata about the corresponding host and operating system.
5555

56+
:::{note}
57+
The `from_context: client_metadata` option in the `resource` processor only applies to transport-level metadata. It cannot extract custom application attributes.
58+
59+
To propagate such values into your telemetry, set them explicitly in your application code using EDOT SDK instrumentation. For more information, refer to [EDOT Collector doesn’t propagate client metadata](docs-content://troubleshoot/ingest/opentelemetry/edot-collector/metadata.md).
60+
:::
61+
5662
Data is exported directly to {{es}} using the [`elasticsearch`] exporter in `OTel-native` mode.
5763

5864
#### Application and traces collection pipeline

0 commit comments

Comments
 (0)