Skip to content

Commit 6619cb0

Browse files
authored
fix: update k8sprocessor link (#4555)
## Changes The k8sprocessor was renamed the k8sattributes processor some time ago. This is updating the spec to point to the correct place. * [ ] [`CHANGELOG.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/CHANGELOG.md) file updated for non-trivial changes Signed-off-by: alex boten <223565+codeboten@users.noreply.github.com>
1 parent cc082a5 commit 6619cb0

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

specification/logs/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ data models, send the data through OpenTelemetry Collector, where it can be
107107
enriched and processed in a uniform manner. For example, Collector can add to
108108
all telemetry data coming from a Kubernetes Pod several attributes that describe
109109
the pod and it can be done automatically using
110-
[k8sprocessor](https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sprocessor?tab=doc)
110+
[k8sattributesprocessor](https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sattributesprocessor?tab=doc)
111111
without the need for the Application to do anything special. Most importantly
112112
such enrichment is completely uniform for all 3 signals. The Collector
113113
guarantees that logs, traces and metrics have precisely the same attribute names

0 commit comments

Comments
 (0)