# Log Enrichment

**URL:** <https://community.dynatrace.com/t/log-enrichment/44147>\
**Category:** Logs\
**Tags:** log-monitoring-class\
**Created:** [February 15, 2024, 3:14pm UTC](https://community.dynatrace.com/t/log-enrichment/44147 "2024-02-15T15:14:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![SureshThakur](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@SureshThakur](https://community.dynatrace.com/u/SureshThakur)\
**Post date:** [February 15, 2024, 3:14pm UTC](https://community.dynatrace.com/t/log-enrichment/44147/1 "2024-02-15T15:14:12Z")

</div>

Hi,

We have Kubernetes monitoring enabled by Dynatrace with log monitoring disabled. However, we can see Dynatrace still adding dt.span\_id, dt.trace\_id etc attributes to the logs of application pod.

Is there way we can disable the auto enrichment for specific Kubernetes cluster or specific entity.

Regards

Suresh

---

<div class="post-metadata">

**Author:** ![bsnurka](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/bsnurka/32/26730_2.png) [@bsnurka](https://community.dynatrace.com/u/bsnurka)\
**Post date:** [February 15, 2024, 4:27pm UTC](https://community.dynatrace.com/t/log-enrichment/44147/2 "2024-02-15T16:27:39Z")

</div>

Hey&nbsp;[@SureshThakur](https://community.dynatrace.com/user/57497)&nbsp;, to my knowledge, once OA is ingesting the logs (even if monitoring is disabled), the automatic enrichment takes place which will add those attributes you are referring to:&nbsp;[Automatic log enrichment — Dynatrace Docs](https://docs.dynatrace.com/docs/observe-and-explore/logs/lma-log-ingestion-via-oa/lma-log-data-transformation-oa)

How is your Dynakube configured currently? Does only an AG Spec exist in the Dybakube cr yaml or does it also include an OA spec? Example [Kubernetes Observability YAML](https://github.com/Dynatrace/dynatrace-operator/blob/main/assets/samples/dynakube/kubernetesObservability.yaml).

---

<div class="post-metadata">

**Author:** ![SureshThakur](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@SureshThakur](https://community.dynatrace.com/u/SureshThakur)\
**Post date:** [February 20, 2024, 6:17am UTC](https://community.dynatrace.com/t/log-enrichment/44147/3 "2024-02-20T06:17:27Z")

</div>

Hi&nbsp;[@bsnurka](https://community.dynatrace.com/user/70552)&nbsp;,

Thanks for your response. I got a confirmation from support as well on the same.

For disabling the log enrichment, we have 2 options.

Either disable in the global setting or at process group level. We have set the rule at PG level, and it has worked.

Regards

Suresh

---

<div class="post-metadata">

**Author:** ![safumod](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@safumod](https://community.dynatrace.com/u/safumod)\
**Post date:** [February 24, 2025, 8:23pm UTC](https://community.dynatrace.com/t/log-enrichment/44147/4 "2025-02-24T20:23:16Z")

</div>

Hey Suresh,

I am struggling with the same issue on ECS Fargate can you please let me know what rule do we need to set at process group level ?

Thanks