out_exec vs out_exec_filter

[micha...@rubikloud.com]

Hi,

Am trying to write an output filter to publish events to a custom queue - however, it seems that out_exec requires calling the command line for every event, which sounds very inefficient.

Is there a way to keep only 1 instance of the external command running, which listens to its STDIN, much like out_exec_filter?  As I understand both in_exec and out_exec_filter runs the external command only once.

If out_exec doesn't do it, I probably will need to use out_exec_filter, with a new tag_key replacement that will match to type @null?

Thanks,

Michael

[Mr. Fiber]

Sorry, I can't understand your situation correctly.

out_exec is not filter like plugin, so out_exec_filter can't be a replacement.

> it seems that out_exec requires calling the command line for every event,

Incorrect. See official article first: http://docs.fluentd.org/articles/out_exec

Masahiro

--
You received this message because you are subscribed to the Google Groups "Fluentd Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fluentd+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mr. Fiber]

And what does "custom queue" mean?

Do you need to re-emit filtered events into fluentd pipeline?