Skip to content

Commit d470d96

Browse files
ericywltheletterf
andauthored
Fix data stream routing wording (#1276)
Apply suggestion from #1260 (comment). Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
1 parent df51125 commit d470d96

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

solutions/observability/apm/data-stream-routing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,6 @@ Elastic APM supports [routing APM data](/solutions/observability/apm/data-stream
1313

1414
To automatically route OTLP data, set the `data_stream.dataset` and `data_stream.namespace` attributes. These attributes map to the respective [ECS fields](ecs://reference/ecs-data_stream.md).
1515

16-
You can set the `data_stream` attributes at resource level, scope level, span level, or span event level. Elastic parses the attributes in increasing order of precedence. For example, span event `data_stream` attributes override the span `data_stream` attributes. This implies that `data_stream` attributes are inherited from previous levels. If a span doesn't specify `data_stream` attributes, it uses the scope attributes.
16+
You can set the `data_stream` attributes at resource level, scope level, and record level. Elastic parses the attributes in increasing order of precedence. For example, record `data_stream` attributes override the scope `data_stream` attributes. This implies that `data_stream` attributes are inherited from previous levels. If a scope does not specify `data_stream` attributes, it uses the resource attributes.
1717

1818
For guidance on how to set resource attributes in OpenTelemetry, refer to [setting resource attributes](/solutions/observability/apm/attributes.md#setting-resource-attributes).

0 commit comments

Comments
 (0)