[Telemetry Operator] Concept on how to enable kubelet logs as input #560
Labels
area/logs
LogPipeline
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Description
With having a dedicated log gateway as part of this epic, a next natural step is to include k8s events as one input for logs. The otel-collector already ships a dedicated receiver for that: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/k8seventsreceiver
Goal: Build up understanding and try out the receiver to come up with a concrete action plan
Criterias
The text was updated successfully, but these errors were encountered: