# CustomLogs integration turns unhealthy with simple wildcard change

**URL:** <https://discuss.elastic.co/t/customlogs-integration-turns-unhealthy-with-simple-wildcard-change/345423>\
**Category:** Elastic Agent\
**Tags:** integrations\
**Created:** [October 19, 2023, 10:36pm UTC](https://discuss.elastic.co/t/customlogs-integration-turns-unhealthy-with-simple-wildcard-change/345423 "2023-10-19T22:36:30Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![CiscoMT](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ciscomt/32/126708_2.png) [@CiscoMT](https://discuss.elastic.co/u/CiscoMT)\
**Post date:** [October 26, 2023, 3:53pm UTC](https://discuss.elastic.co/t/customlogs-integration-turns-unhealthy-with-simple-wildcard-change/345423/6 "2023-10-26T15:53:34Z")

</div>

Will create a new threat, Thanks following up @stephenb, appreciate the help!

Regarding the \*.log part, funny, I didn't read that in the docs actually. It was a comment you left in some other topic a while ago hehe. Maybe I missed something and this doesn't apply to the custom logs integration.

[Link here](https://discuss.elastic.co/t/path-config-for-custom-log-integration/262158/4)

---

_[View the full topic](https://discuss.elastic.co/t/customlogs-integration-turns-unhealthy-with-simple-wildcard-change/345423)._