# Before enable deep monitoring for a pod or namespace the memory resource check is required

**URL:** <https://community.dynatrace.com/t/before-enable-deep-monitoring-for-a-pod-or-namespace-the-memory-resource-check-is-required/50195>\
**Category:** Dynatrace Tips\
**Tags:** openshift, kubernetes\
**Created:** [February 11, 2025, 8:27am UTC](https://community.dynatrace.com/t/before-enable-deep-monitoring-for-a-pod-or-namespace-the-memory-resource-check-is-required/50195 "2025-02-11T08:27:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mizso74](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@mizso74](https://community.dynatrace.com/u/mizso74)\
**Post date:** [February 11, 2025, 8:27am UTC](https://community.dynatrace.com/t/before-enable-deep-monitoring-for-a-pod-or-namespace-the-memory-resource-check-is-required/50195/1 "2025-02-11T08:27:21Z")

</div>

Hi Folks,

Based on the documnetation there is a memory overhead of the dynatrace code module (100 - 200 MB).

[OneAgent memory requirements — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/memory-requirements)

Nowdays I met some kubernetes / openshift clusters with very limited memeory resources. I have created a high level qucik dashboard, to check the memory limit and memory usage metrics. Free memory limit / pod&nbsp; should be higher than the overhead.

 ![Mizs_0-1739262074745.png](https://global.discourse-cdn.com/dynatrace/original/2X/b/b2c56d17b85312b2cc70005b6eca629445debdc2.png)

 ![Mizs_1-1739262275106.png](https://global.discourse-cdn.com/dynatrace/original/2X/d/d40cc85c41a6689bf08a3deaf81cd593c04d0840.png)

Maybe it is useful for you also.

Best regards,

János
