Skip to content

Commit 4e910af

Browse files
Update content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md
Co-authored-by: Cyrille Le Clerc <[email protected]>
1 parent 6043c36 commit 4e910af

File tree

1 file changed

+3
-6
lines changed
  • content/en/blog/2024/collecting-otel-compliant-java-logs-from-files

1 file changed

+3
-6
lines changed

content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md

+3-6
Original file line numberDiff line numberDiff line change
@@ -313,12 +313,9 @@ After the pipeline works end-to-end, ensure production readiness:
313313

314314
## Configure an OpenTelemetry Collector in Kubernetes to handle container logs
315315

316-
To support Kubernetes and container specifics, add a standard parsing step in
317-
the pipeline without specific mapping configuration.
318-
319-
Use the OTel Collector File Log Receiver's
320-
[`container`](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/docs/operators/container.md)
321-
parser to handle container logging specifics.
316+
To support Kubernetes and container specifics, add the built-in
317+
[`container`](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/docs/operators/container.md)
318+
parsing step in the pipeline without needing specific mapping configuration.
322319

323320
Replace `<<namespace>>`, `<<pod_name>>`, and `<<container_name>>` with the
324321
desired values or use a broader [glob pattern](https://pkg.go.dev/v.io/v23/glob)

0 commit comments

Comments
 (0)