Skip to content

update stability and a warning note for k8s attribute processor #5957

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 23, 2025
Merged

update stability and a warning note for k8s attribute processor #5957

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
72aeffd
update stability and a warning note for k8s attribute processor
Oct 23, 2025
2ec3df3
Updates from review
jpipkin1 Oct 23, 2025
b93b8a6
small typo on the doc
Oct 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/send-data/kubernetes/v4/important-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,12 +17,12 @@ Prometheus 3.0 includes several breaking changes. Learn more about those changes

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.

### Kubernetes Attributes Processor support (v4.13)
### Kubernetes Attributes Processor support ( alpha/development )

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`.

:::note
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.
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.
:::

### Remove Fluent Bit and Fluentd
Expand Down