I have a device sending syslogs in standard kv pair format; with a comma (,) separating fields and equal (=) separating key from value.
sample:
key1="value1",key2="value2",key3="value3",...
In order to ensure ECS compatibility, I have a kv filter defined with a "target" field set.
In Elastic, I am expecting to only see the kv-parsed fields in the nested field but I am seeing them both at the root AND in the nested field.
Is there some "automatic" parsing that logstash does? If not, why do I see all of these fields at the document root as well as the nested field?