Skip to content

Commit 9c3d44b

Browse files
samiurajpipkin1
andauthored
update stability and a warning note for k8s attribute processor (#5957)
* update stability and a warning note for k8s attribute processor * Updates from review * small typo on the doc --------- Co-authored-by: John Pipkin <[email protected]>
1 parent 9e95082 commit 9c3d44b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/send-data/kubernetes/v4/important-changes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,12 @@ Prometheus 3.0 includes several breaking changes. Learn more about those changes
1717

1818
Use Helm chart [v4.14.0](https://github.com/SumoLogic/sumologic-kubernetes-collection/releases/tag/v4.14.0) or later to ensure compatibility with Prometheus 3.0 scrapers. Note that Prometheus 3.0 is not the default in Helm chart version 4.
1919

20-
### Kubernetes Attributes Processor support (v4.13)
20+
### Kubernetes Attributes Processor support ( alpha/development )
2121

2222
The [Kubernetes Attributes Processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/k8sattributesprocessor/README.md) is now supported for logs and metrics metadata enrichment. This processor is disabled by default. To enable this processor for logs, set `metadata.logs.useSumoK8sProcessor` to `false`. To enable this processor for metrics, set `metadata.metrics.useSumoK8sProcessor` to `false`.
2323

2424
:::note
25-
The Service name is part of the metadata enrichment with this processor in v4.15.0. Refer to the [OpenTelemetry service name calculation documentation](https://opentelemetry.io/docs/specs/semconv/non-normative/k8s-attributes/#how-servicename-should-be-calculated) to understand how the service name is calculated.
25+
The service name is part of the metadata enrichment with this processor in v4.15.0. Refer to the [OpenTelemetry service name calculation documentation](https://opentelemetry.io/docs/specs/semconv/non-normative/k8s-attributes/#how-servicename-should-be-calculated) to understand how the service name is calculated. Initially switching to this processor from the existing `k8s_tagger` processor may cause an incorrect association of logs with Kubernetes metadata for a certain period of time.
2626
:::
2727

2828
### Remove Fluent Bit and Fluentd

0 commit comments

Comments
 (0)