Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
filters/clone/conditionals bug #1548
I am not sure what the source of this issue is but right now my brain is fried so I'll post it here for others to look at it, and when my brain is unfried I'll work on it.
with this configurations
type in any input, "foo" for example
clearly, the 2nd event, the clone, did not correctly went through the
It seems like any event created by a filter can cause this, all future conditionals are ignored.
Dumping this data into /tmp/bugData.log
Same result doing it with the metric plugin, and another one I wrote 'alert'. The events are created by the filter and picked up by 'flush'. I initially used event.append to merge two events but then switched to just created each field from the original events. Same end result.
I had read in the Jira someone states the conditionals were honoring the base event, but that is not what I am seeing. They are just being ignored all together on the created event.
Found a comment from October/2013 suggesting using type/tags deprecated conditionals. Confirmed these work. :)
added a commit
Sep 5, 2014
added a commit
Dec 2, 2014
Think, it has been solved! But the documentation is not clear about the semantics of the clone behavior!
@mjscosta Indeed it's been solved. Good note about the documentation not being clear - can you file a new ticket about getting that documented?
To answer your question, your last detail is correct in describing the behavior -- this is right: