# Not able to ingest application log files using OneAgent on a Fargate container

**URL:** <https://community.dynatrace.com/t/not-able-to-ingest-application-log-files-using-oneagent-on-a-fargate-container/46166>\
**Category:** Logs\
**Tags:** aws, log-monitoring-class, oneagent\
**Created:** [June 18, 2024, 2:33am UTC](https://community.dynatrace.com/t/not-able-to-ingest-application-log-files-using-oneagent-on-a-fargate-container/46166 "2024-06-18T02:33:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![paul2perth](https://avatars.discourse-cdn.com/v4/letter/p/e8c25b/32.png) [@paul2perth](https://community.dynatrace.com/u/paul2perth)\
**Post date:** [June 18, 2024, 2:33am UTC](https://community.dynatrace.com/t/not-able-to-ingest-application-log-files-using-oneagent-on-a-fargate-container/46166/1 "2024-06-18T02:33:34Z")

</div>

I have deployed OneAgent onto my Fargate container which is primarily running nginx and Flask/Python with uWSGI.

The container shows as a host through Hosts Classic fine.

- The application log file is written to /var/log/app/ as action.log which should meet the security criteria.
- The container root file system is read-only.
- A number of volumes and mount points have been added for
  - logging nginx and uWSGI,
  - OneAgent logs and datastorage,
  - /tmp and
  - /var/log/app directory structure.

Under the host I’m not seeing any automatically detected logs so have tried to add /var/log/app

I have added

- A custom log source, against the nginx log source context and path /var/log/app/\*
- A log ingest rule for /var/log/app/action.log

Despite this I am still not able to see the logs being ingested in Logs & Events.

I do have logs ingesting from my EC2 hosts without issue.

Any help would be welcome.

Cheers

---

<div class="post-metadata">

**Author:** ![PacoPorro](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pacoporro/32/36087_2.png) [@PacoPorro](https://community.dynatrace.com/u/PacoPorro)\
**Post date:** [June 18, 2024, 7:22am UTC](https://community.dynatrace.com/t/not-able-to-ingest-application-log-files-using-oneagent-on-a-fargate-container/46166/2 "2024-06-18T07:22:32Z")

</div>

With fargate you should go through fluent bit

> **[Stream logs to Dynatrace with Fluent Bit](https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-log-ingestion/lma-stream-logs-with-fluent-bit)**
>
> Integrate Fluent Bit to stream logs to Dynatrace.

---

<div class="post-metadata">

**Author:** ![ASE](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@ASE](https://community.dynatrace.com/u/ASE)\
**Post date:** [October 3, 2024, 2:18am UTC](https://community.dynatrace.com/t/not-able-to-ingest-application-log-files-using-oneagent-on-a-fargate-container/46166/3 "2024-10-03T02:18:23Z")

</div>

Hello, [@paul2perth](https://community.dynatrace.com/user/51688).

This behavior sounds very similar to what we’re experiencing with our ECS/Fargate Containers.

When I view an ECS/EC2 Cluster in the **Hosts** app, it automatically detects all available Log Sources.

But when I view an ECS/Fargate Cluster in the **Containers** app, it does not automatically detect all available Log Sources.

Both configs have OneAgent installed.

The issue could be related to us using ECS/Fargate. 🤔

Perhaps the info provided to me can help you with your troubleshooting:

[https://community.dynatrace.com/t5/Container-platforms/Container-Logs-Not-Found-Containers-App/m-p/257905#M2668](https://community.dynatrace.com/post/257905#M2668)
