# Unable to process multiple logs **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [January 7, 2016, 8:04am UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577 "2016-01-07T08:04:42Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![hw96](https://avatars.discourse-cdn.com/v4/letter/h/a9adbd/32.png) [@hw96](https://discuss.elastic.co/u/hw96)\ **Post date:** [January 7, 2016, 8:04am UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577/1 "2016-01-07T08:04:42Z")
Hi, I'm relatively new to Filebeat in general and I'm currently facing the problem of being unable to process multiple logs under a single "paths" segment. In my case, only the first log is processed whereas the rest are left untouched. ![](https://us1.discourse-cdn.com/elastic/original/2X/9/9fd64a6170818874dd7d31c80549bde19fc0cb57.png) I've also tried using the "path/\*.log" method but only cron logs specifically are processed. Please kindly provide me with some assistance. ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [January 7, 2016, 8:28am UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577/2 "2016-01-07T08:28:47Z")
Is there anything interesting in the logs if you max out the loglevel settings by starting Filebeat with `-d "*"`? Next time please don't post screenshots. Copy/paste the text instead and format it as code (there's a toolbar button for it). ---
**Author:** ![hw96](https://avatars.discourse-cdn.com/v4/letter/h/a9adbd/32.png) [@hw96](https://discuss.elastic.co/u/hw96)\ **Post date:** [January 7, 2016, 8:31am UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577/3 "2016-01-07T08:31:09Z")
Sorry about that, I'm still quite new to the forum. I forgot to state this but the logs are all back from 2014 ---
**Author:** ![hw96](https://avatars.discourse-cdn.com/v4/letter/h/a9adbd/32.png) [@hw96](https://discuss.elastic.co/u/hw96)\ **Post date:** [January 7, 2016, 9:54am UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577/4 "2016-01-07T09:54:30Z")
Can I ask how do you do that? ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [January 7, 2016, 10:16am UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577/5 "2016-01-07T10:16:56Z")
Sorry, do what? ---
**Author:** ![hw96](https://avatars.discourse-cdn.com/v4/letter/h/a9adbd/32.png) [@hw96](https://discuss.elastic.co/u/hw96)\ **Post date:** [January 7, 2016, 10:23am UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577/7 "2016-01-07T10:23:53Z")
" starting Filebeat with -d "\*" " ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [January 7, 2016, 10:31am UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577/8 "2016-01-07T10:31:43Z")
I'm not sure how to explain that differently; add `-d "*"` to your Filebeat command line: ``` filebeat ... -d "*" ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 9:56pm UTC](https://discuss.elastic.co/t/unable-to-process-multiple-logs/38577/9 "2017-07-05T21:56:57Z")