# Nginx Logs Can't Be Parsed Because Symlinks

**URL:** https://discuss.elastic.co/t/nginx-logs-cant-be-parsed-because-symlinks/323958
**Category:** Beats
**Tags:** filebeat
**Created:** [January 25, 2023, 6:21pm UTC](https://discuss.elastic.co/t/nginx-logs-cant-be-parsed-because-symlinks/323958 "2023-01-25T18:21:19Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Tetiana\_Kravchenko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tetiana_kravchenko/32/102683_2.png) [@Tetiana\_Kravchenko](https://discuss.elastic.co/u/Tetiana_Kravchenko)
#### Post date: [January 26, 2023, 10:55am UTC](https://discuss.elastic.co/t/nginx-logs-cant-be-parsed-because-symlinks/323958/2 "2023-01-26T10:55:49Z")

</div>

Hello @Christian_Jacobs

Filebeat does not support non-standard files. Similar question can be found in this [thread](https://discuss.elastic.co/t/will-filebeat-be-able-read-dev-stdout-and-dev-stderr/88880).

As an option you can consider running filebeat as a separate container. You can check this [page](https://www.elastic.co/guide/en/beats/filebeat/current/running-on-docker.html) for running filebeat in docker, or [this](https://www.elastic.co/guide/en/beats/filebeat/current/running-on-kubernetes.html) for running in kubernetes.

---

_[View the full topic](https://discuss.elastic.co/t/nginx-logs-cant-be-parsed-because-symlinks/323958)._