# How do we ingest files into Dynatrace SaaS that has .json?

**URL:** <https://community.dynatrace.com/t/how-do-we-ingest-files-into-dynatrace-saas-that-has-json/44249>\
**Category:** Open Q&A\
**Tags:** dynatrace-saas, oneagent\
**Created:** [February 22, 2024, 1:30pm UTC](https://community.dynatrace.com/t/how-do-we-ingest-files-into-dynatrace-saas-that-has-json/44249 "2024-02-22T13:30:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![karthikr](https://avatars.discourse-cdn.com/v4/letter/k/eada6e/32.png) [@karthikr](https://community.dynatrace.com/u/karthikr)\
**Post date:** [February 22, 2024, 1:30pm UTC](https://community.dynatrace.com/t/how-do-we-ingest-files-into-dynatrace-saas-that-has-json/44249/1 "2024-02-22T13:30:46Z")

</div>

Team,

Can anyone please let me know how do we ingest files with .json extension onto Dynatrace SAAS environment? I am able to ingest files with .log extension but not files with .json extension.

---

<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:** [February 22, 2024, 1:43pm UTC](https://community.dynatrace.com/t/how-do-we-ingest-files-into-dynatrace-saas-that-has-json/44249/2 "2024-02-22T13:43:56Z")

</div>

Please check [custom log source](https://docs.dynatrace.com/docs/shortlink/lma-custom-log-source) doc and pay special attention to the [security rules .](https://docs.dynatrace.com/docs/shortlink/lma-custom-log-source#override-security-rules)

---

<div class="post-metadata">

**Author:** ![karthikr](https://avatars.discourse-cdn.com/v4/letter/k/eada6e/32.png) [@karthikr](https://community.dynatrace.com/u/karthikr)\
**Post date:** [February 22, 2024, 2:19pm UTC](https://community.dynatrace.com/t/how-do-we-ingest-files-into-dynatrace-saas-that-has-json/44249/3 "2024-02-22T14:19:21Z")

</div>

Thanks&nbsp;[@PacoPorro](https://community.dynatrace.com/user/40713)&nbsp;for your response. I believe I had gone through this already. In-fact I created .json file under this path&nbsp;/var/lib/dynatrace/oneagent/agent/config/logmodule to allow .json file to discover by OneAgent.

{  
“@version”: “1.0.0”,  
“allowed-log-paths-configuration”: [  
{  
“directory-pattern”: “/tmp/”,  
“file-pattern”: “\*.json”,  
“action”: “INCLUDE”  
}  
]  
}

I included the above content as the json file to override the security rules, but however after configuring Ingest rules and when trying to add json file path under Custom Log Source, I am seeing below warning message.

Provided value contains following potential issues:

- not recognized as log, may not be allowed due to security rules

And when I look at the Host page for log sources, it says the following,

/tmp/example1.json (No log data available)

I am not sure what I am doing wrong with any of the configuration, please advise.

---

<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:** [February 22, 2024, 3:17pm UTC](https://community.dynatrace.com/t/how-do-we-ingest-files-into-dynatrace-saas-that-has-json/44249/4 "2024-02-22T15:17:13Z")

</div>

Could you please check in the&nbsp;&nbsp;Log Agent’s own logs?

---

<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:** [February 22, 2024, 3:46pm UTC](https://community.dynatrace.com/t/how-do-we-ingest-files-into-dynatrace-saas-that-has-json/44249/5 "2024-02-22T15:46:50Z")

</div>

I just tested it in my lab and it works.

 ![PacoPorro_0-1708616323536.png](https://global.discourse-cdn.com/dynatrace/original/3X/4/3/432689d2c71789edc6a9730e0e29d794d5bf6d3a.png)

 ![PacoPorro_1-1708616564073.png](https://global.discourse-cdn.com/dynatrace/original/3X/5/8/5853ff2973a327669b9eaf8fea57f4a8c1af451a.png)

I created your rule

 ![PacoPorro_2-1708616632726.png](https://global.discourse-cdn.com/dynatrace/original/3X/b/f/bf08491ba7f77f25ae0c2b51e265ba65df3a50ae.png)

Agent restarted just in case.&nbsp;  
Custom log source created. I ignored the security rule warning.

 ![PacoPorro_3-1708616709092.png](https://global.discourse-cdn.com/dynatrace/original/2X/9/9e802463b891d81bb99b189dfd96b9accc3d4f36.png)

Added the ingest rule.

 ![PacoPorro_4-1708616786639.png](https://global.discourse-cdn.com/dynatrace/original/3X/2/d/2d55c03e9a7f7dd122490b5b68005d918f1a53fe.png)

---

<div class="post-metadata">

**Author:** ![karthikr](https://avatars.discourse-cdn.com/v4/letter/k/eada6e/32.png) [@karthikr](https://community.dynatrace.com/u/karthikr)\
**Post date:** [February 22, 2024, 4:21pm UTC](https://community.dynatrace.com/t/how-do-we-ingest-files-into-dynatrace-saas-that-has-json/44249/6 "2024-02-22T16:21:52Z")

</div>

Thank you so much&nbsp;[@PacoPorro](https://community.dynatrace.com/user/40713)&nbsp;for testing it so quickly. I believe the issue was related to the timestamp key/value pairs that I was using in the .json file, when I created new event with latest timestamp after enabling the log ingesting rules + custom log source path, it worked. I will continue to perform the testing. Thanks for all your help.
