Hi all, Very supportive of this. I've always thought that Flume is a great alternative to fluentd and could easily provide an enhanced capability set (Kafka, Log4J , JMS, etc) and simple scale out architecture. Open telemetry native support would be great, as would deployment via Kubernetes.
I started work on a Docker build here https://github.com/apache/flume/pull/351 which could be used as the basis as a Kubernetes deployment and no reason why we couldn't follow up with an Operator as well. At the time we lacked any committers with enough expertise to validate the approach, and then the maven plugin got deprecated, but if there's anyone with the expertise to pick this up, I'd be more than happy to support however I can. Unlocking deployability of Flume is key to its survival IMHO. Tristan ________________________________ From: Matt Sicker <m...@musigma.org> Sent: Friday, December 1, 2023 5:28:14 pm To: dev@logging.apache.org <dev@logging.apache.org> Subject: Re: [Flume] Integration with OpenTelemetry > On Nov 30, 2023, at 12:13 PM, Christian Grobmeier <grobme...@apache.org> > wrote: > > Please do. I would also like to learn more about this stuff and maybe we can > make Chainsaw to receive Flume messages or OTel things too! I think that would make sense. When I do a deeper review of OpenTelemetry, I’ll suggest what components here can integrate with what.
