Thanks for taking the time to read these lines,
I've got a question regarding kv filter and its allow_duplicate_values attribute
Assuming I have a log that looks like :
1/ How come ? I thought allow_duplicate_values=false would have kept either value1 or value4 but not both
2/ Actually, it would appear that I'm happy with this 2nd output, but is there a way to change the separator , and use : ?
1/ Sorry, what do you mean by "you always get both". In which format would I get both values ? from: "Badger,Badger" ?
2/ Downstream in the same logstash conf I'm doing :
add_field => { "a_new_key" => "%{key2}:%{key1}" }
So it was fine until I start seeing a few : a_new_key: "value2:value1,value4" (taking back my example of my post)
Do you think the conversion to string would have added the comma ?
I'm ideally looking for a way to get a_new_key: "value2:value1" when I have twice key1=value1 in my logs and a_new_key: "value2:value1:value4" when I have key1=value1|...|key1=value4
If I can bother you with one more question, how would Elasticsearch react to from=Badger from=GitsBdr ? It would first create the document with a field from and the value Badger and then update it with the value GitsBdr ?
And Logstash ? I quite don't get how would you separately manipulate these 2 values if they have the same key name !
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.