# Elastic Agent Logs from UNC Path?

**URL:** <https://discuss.elastic.co/t/elastic-agent-logs-from-unc-path/354847>\
**Category:** Elastic Agent\
**Tags:** filebeat\
**Created:** [March 6, 2024, 1:46pm UTC](https://discuss.elastic.co/t/elastic-agent-logs-from-unc-path/354847 "2024-03-06T13:46:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)\
**Post date:** [March 6, 2024, 1:46pm UTC](https://discuss.elastic.co/t/elastic-agent-logs-from-unc-path/354847/1 "2024-03-06T13:46:14Z")

</div>

I am using Elastic Agent 8.12.1 on a Windows host. I have a requirement to ingest logs for an application which writes them directly to a share referenced UNC path from the host (e.g., `\\myshare\myapp\logs\log.json`). That share is NOT mounted as a drive and I'm not able to configure the hosts to mount it.

I'm using Elastic Agent with the Filestream integration. It does NOT appear to recognize the logs from the UNC path. In the past, I was able to do this with Filebeat directly, IIRC. I realize that it's recommended to NOT read logs from network shares, but that it will work. Is there any way to force the Filestream integration to work with a UNC path?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 3, 2024, 1:46pm UTC](https://discuss.elastic.co/t/elastic-agent-logs-from-unc-path/354847/2 "2024-04-03T13:46:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.