Note that the message field is usually a text field and you would have to add a new mapping setting your new custom field to text for it to be searchable like mesage
grok {
match => {'anyotherfield' => ' <here are parsed fields> %{GREEDYDATA:message}'}
}
For instance, you can: match => {'[event][original]' => ' <here are parsed fields> %{GREEDYDATA:message}'}
If you use 'message' => '...parsed fields... %{GREEDYDATA:message}' then you will get an array [message][0]=old_(orginal)_data and [message][1]=message_from_greedydata. In that case, to avoid, you can use overwrite the message.
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.