There’s a standing issue with example solutions that covers the listen socket part, but any matching would have to be done client-side.
https://github.com/mozilla-services/heka/issues/1527 -- Jonathan Owens Site Engineering On June 24, 2015 at 05:00:09, [email protected] ([email protected]) wrote: Message: 2 Date: Tue, 23 Jun 2015 23:53:22 +0000 From: David Birdsong <[email protected]> To: heka <[email protected]> Subject: [heka] dynamic message matcher on output Message-ID: <cabjfl5gjmzfmt8kpzftoqrtvnardh1od2625mdv602jevmc...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" I keep running into a use-case where an inverted output plugin would be super-useful. Something like a websocket where as part of the request, the caller can specify a message matcher that gets registered w/ the router but deregistered when the connection goes away. Raw TCP would be fine too if there was a sensible way to specify the match syntax. This is really more of a pub/sub system, but one that can tap the streams of data going through heka while filtering out using the rich matching. If a dynamic filter can do add a new message_matcher, is there anything in the way of making that available to output plugins?
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
