# Kubernetes.container.memory.usage.bytes looks incorrect for redis container

**URL:** <https://discuss.elastic.co/t/kubernetes-container-memory-usage-bytes-looks-incorrect-for-redis-container/249110>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [September 18, 2020, 1:44pm UTC](https://discuss.elastic.co/t/kubernetes-container-memory-usage-bytes-looks-incorrect-for-redis-container/249110 "2020-09-18T13:44:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![willis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willis/32/75826_2.png) [@willis](https://discuss.elastic.co/u/willis)\
**Post date:** [September 18, 2020, 1:44pm UTC](https://discuss.elastic.co/t/kubernetes-container-memory-usage-bytes-looks-incorrect-for-redis-container/249110/1 "2020-09-18T13:44:10Z")

</div>

I have a redis pod with container limits of 6GB. Metricbeat (7.6.2) data from the container shows:

```auto
kubernetes.container.memory.usage.bytes: 5.9GB
kubernetes.container.memory.usage.limit.pct: 99.9%
kubernetes.container.memory.available.bytes: 1.6GB

```

This container looks to be using 100% of available memory but also has 1.6GB available? We base our alerts on `kubernetes.container.memory.usage.limit.pct` so this is problematic right now. Any idea whats going on? I can provide a screenshot if it helps. From some limited sampling, other containers in the clusters correctly show the kubernetes.container.memory.usage.limit.pct as a reflection of the k8s manifest limit.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 16, 2020, 3:44pm UTC](https://discuss.elastic.co/t/kubernetes-container-memory-usage-bytes-looks-incorrect-for-redis-container/249110/2 "2020-10-16T15:44:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.