Agreed, the tag is confusing to us too.
On Graylog, if I have 3 configurations.
- Config1 - tag1
- Config2 - tag2
- Config3 - tag3
On the collector side, I was wrongly expecting that if I set tag1 and tag2,
the client would get both configurations.
But that didn't work
Because each configuration to be configured needs its own output, and the
generated nxlog.conf did not get the two outputs or the auto-generated two
routes.
I think Inputs, Outputs, Snippets and even routes (which cannot be defined
now) need to be decoupled from a configuration and be allowed to be defined
independently each in its own collections (similar to how the rules are
done in pipelines) for convenience (you don't want to repeat for each
config) and functionality (see below the nxlog internal example)
Then a configuration can pull one or many of the above components from the
collections, and then applied to a collector.
If we don't decouple, then if we want to have nxlog internal logs logged to
Graylog, we would need to define something like this in Snippets for each
config (repeated and modified to match the output id)
<Input internal>
Module im_internal
</Input>
<Route internal>
Path internal => 977ad164136aa0330cf2b422
</Route>
and if the client has multiple tags, would it get multiple copies? single
copy? which output? which route?
Sorry if we're understanding this thing totally wrong.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/0eb49603-18b4-4e1e-98f7-02ccfd35ef08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
