# Logs in JSON from OneAgent on K8S vs Logs from Log Ingest API

**URL:** <https://community.dynatrace.com/t/logs-in-json-from-oneagent-on-k8s-vs-logs-from-log-ingest-api/51928>\
**Category:** Logs\
**Tags:** dql, log-processing, kubernetes, logs\
**Created:** [June 3, 2025, 4:05pm UTC](https://community.dynatrace.com/t/logs-in-json-from-oneagent-on-k8s-vs-logs-from-log-ingest-api/51928 "2025-06-03T16:05:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aymeric\_M](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/aymeric_m/32/35713_2.png) [@Aymeric\_M](https://community.dynatrace.com/u/Aymeric_M)\
**Post date:** [June 3, 2025, 4:05pm UTC](https://community.dynatrace.com/t/logs-in-json-from-oneagent-on-k8s-vs-logs-from-log-ingest-api/51928/1 "2025-06-03T16:05:09Z")

</div>

Hi,

There is a weird difference in Logs New (and also in Classic) between logs in JSON format received from K8S by OneAgent and logs in JSON format received from the Log Ingest API.

The logs from the API seem to be pre-parsed and all the attributes are available as fields for filtering whereas logs from OneAgent are not and we have to switch to DQL query mode and add JSON parsing commands.

Is there a way to have the logs coming from OneAgent pre-parsed ?

Note that I already checked if we have a preprocessing rule that would apply on logs from the API and it is not the case.

---

<div class="post-metadata">

**Author:** ![AntonPineiro](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antonpineiro/32/49_2.png) [@AntonPineiro](https://community.dynatrace.com/u/AntonPineiro)\
**Post date:** [June 3, 2025, 4:34pm UTC](https://community.dynatrace.com/t/logs-in-json-from-oneagent-on-k8s-vs-logs-from-log-ingest-api/51928/2 "2025-06-03T16:34:40Z")

</div>

Hi,

You can use for [OpenPipeline](https://docs.dynatrace.com/docs/shortlink/openpipeline)&nbsp;processing and parse your logs.

Best regards

---

<div class="post-metadata">

**Author:** ![Aymeric\_M](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/aymeric_m/32/35713_2.png) [@Aymeric\_M](https://community.dynatrace.com/u/Aymeric_M)\
**Post date:** [June 4, 2025, 8:56am UTC](https://community.dynatrace.com/t/logs-in-json-from-oneagent-on-k8s-vs-logs-from-log-ingest-api/51928/3 "2025-06-04T08:56:35Z")

</div>

Yeah, I know that, but I don’t know the content of the logs in advance.  
Is there&nbsp;a DQL or DPL command that will extract all the attributes into fileds without the need to declare each and every one ?  
So far all the examples in the documentation presuppose that we know the name of the attributes that we want to put into fields.
