What's the point of this filter? You're not capturing any fields in the grok expression and you're deleting a number of fields that'll never exist at that point in the pipeline.
I did the changes in my configuration and now it is working as expected.
But i have different folders having logs so how would i configure and also how can i make the index for each.
Ex: /etc/dev/.log
/etc/uat/.log
/etc/int/*.log
I want to set the index for each folder location so that i can able to find environment wise logs. Write now my configuration for only one file path like below. Please guide me to complete this.
I want to set the index for each folder location so that i can able to find environment wise logs.
One index per environment is most likely a bad idea. If you're doing this only to be able to distinguish different kinds of logs just use another field for that. Like the environment field in the configuration you posted previously.
Write now my configuration for only one file path like below.
Why not follow the pattern from the previous post? Apart from what I wrote it looked fine.
grok
{
match => {"message" => "[%WARNING,%INFO]%{GREEDYDATA}[%WARNING]"}
}
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.