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 Original file line number Diff line number Diff line change @@ -313,12 +313,9 @@ After the pipeline works end-to-end, ensure production readiness:
313
313
314
314
## Configure an OpenTelemetry Collector in Kubernetes to handle container logs
315
315
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.
322
319
323
320
Replace ` <<namespace>> ` , ` <<pod_name>> ` , and ` <<container_name>> ` with the
324
321
desired values or use a broader [ glob pattern] ( https://pkg.go.dev/v.io/v23/glob )
You can’t perform that action at this time.
0 commit comments