# Filebeat find error Dropping event: no topic could be selected

**URL:** <https://discuss.elastic.co/t/filebeat-find-error-dropping-event-no-topic-could-be-selected/179876>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 7, 2019, 4:09am UTC](https://discuss.elastic.co/t/filebeat-find-error-dropping-event-no-topic-could-be-selected/179876 "2019-05-07T04:09:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Michal\_Pristas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michal_pristas/32/46639_2.png) [@Michal\_Pristas](https://discuss.elastic.co/u/Michal_Pristas)\
**Post date:** [May 7, 2019, 1:16pm UTC](https://discuss.elastic.co/t/filebeat-find-error-dropping-event-no-topic-could-be-selected/179876/2 "2019-05-07T13:16:20Z")

</div>

there was a reported case [Filebeat Autodiscover Hints Breaking Template](https://discuss.elastic.co/t/filebeat-autodiscover-hints-breaking-template/137310/10)  
when allowing hints started emitting of logs from all the containers even system ones. So I guess if these are emitted and `log_topic` is generated only for the ones matching condition then Kafka topic fallback to empty for others and therefore the error message. This is my guess.

I guess you cannot identify the source of the message. maybe you can play a little with `hints.enabled` to see if it helps

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-find-error-dropping-event-no-topic-could-be-selected/179876)._