Fluentd debug logs are forwarded to custom filter plugin

[john]

Hi all,

           I was trying to add my new custom filter plugin in fluentd. For my self debugging, I tried to print my arguments of the main filter function using log.info . I am seeing that the debug prints are automatically passed again to the plugin filter function with tag fluent.info.  Is it expected? Did i make any mistake somewhere?

Thanks,

John

[Mr. Fiber]

> Is it expected?

Yes. See this section: http://docs.fluentd.org/articles/logging#capture-fluentd-logs

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+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[john]

I am seeing something different. Logs written inside a plugin is received in the same plugin interface. is this expected?

[Mr. Fiber]

>  Logs written inside a plugin is received in the same plugin interface.

What does this sentence mean?

Could you show me the example of your expected behaviour?

[Mr. Fiber]

Ah, you mean following filter receives own log message, right?

<filter fluent.**>

  @type your_filter

</filter>

[john]

yes. You are right

I added <filter> @type your_filter </filter> . This filter receives own log message

[Mr. Fiber]

<filter> @type your_filter </filter> is same as  <filter **> @type your_filter </filter> so all logs are filtered by this plugin.

Currently <filter foo.** bar.**> like your tag list is needed.

Hmm... negate or skip `fluent.**` pattern option may be needed.