Replies: 2 comments
-
same problem |
Beta Was this translation helpful? Give feedback.
-
A label of Fluentd is an independent routing definition without Indeed, something like a filter-only label would be useful to manage multiple combinations of Example: # Source using filter-A
<source>
@label @filter-A
...
</source>
# Source not using filter-A
<source>
@label @output-A
...
</source>
<label @filter-A>
<filter **>...</filter>
<filter **>...</filter>
<match **>
@type relabel
@label @output-A
</match>
</label>
<label @output-A>
<match **>...</match>
</label> |
Beta Was this translation helpful? Give feedback.
-
I tried to use
@label
in order to reduce duplication across multiple filter patterns, however I get this:What I am trying to do:
Unfortunately this doesn't work and I don't want to move the
<match>
inside the<label>
block because it applies to messages from other sources/labels too.Instead I am forced to do this:
Note now that "something.long.and.complicated" is repeated 3 times in my config file which isn't very DRY
Is there a reason can't be used just for without the requirement to have a in there too?
Beta Was this translation helpful? Give feedback.
All reactions