Data Pipelines - Feat. Fluent Bit, Otel Collector, Logging Operator (You Choose!, Ch. 04, Ep. 05)

[@neilboyd3471]

Good job Sandor! Really enjoyed listening to this today.

[@joebowbeer]

Is Telemetry Controller applicable to metrics and traces in addition to logs? (Given that logging is not included in the name.)

[@DevOpsToolkit]

Yeah. The Collector can handle any type of OpenTelemetry, meaning metrics, traces, and logs (with more to come).

[@joebowbeer]

​@@DevOpsToolkitI'm asking about the Telemetry "Controller" (Sandor), which seems to be specific to logging

[@DevOpsToolkit]

My bad. I misread it as collector.

[@sandorguba2671]

In the future yes but not yet. The reason is that handling logs on Kubernetes is tricky as they are stored in privileged storage (Node filesystem). All other signals can be collected "easily" without any indirection (a tenant can scrape their own pods for metrics and the application can be configured to send wherever you push traces). But it would definitely simplify configuration overhead for an administrator so when the logging part is production ready we are going to add the metrics and traces as well. (I don't expect too much work as it is very similarly handled in OTel)