# Wrong host system info from containerized Elastic Agent

**URL:** <https://discuss.elastic.co/t/wrong-host-system-info-from-containerized-elastic-agent/313190>\
**Category:** Elastic Agent\
**Created:** [August 29, 2022, 5:32pm UTC](https://discuss.elastic.co/t/wrong-host-system-info-from-containerized-elastic-agent/313190 "2022-08-29T17:32:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![woodywoodsta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/woodywoodsta/32/107962_2.png) [@woodywoodsta](https://discuss.elastic.co/u/woodywoodsta)\
**Post date:** [August 29, 2022, 5:32pm UTC](https://discuss.elastic.co/t/wrong-host-system-info-from-containerized-elastic-agent/313190/1 "2022-08-29T17:32:46Z")

</div>

I've got a fleet-managed elastic agent which is deployed in my k8s cluster as a Daemonset (as orchestrated by the ECK operator, resource type `Agent`) and it has a policy which includes the `system` integration. It's reporting metric data which appears to match values in `htop` for each host, but the OS info (`host.os.*`) appears to be reflecting the container, not the host.

Is there any way I can get it to retrieve the actual host OS details, and not the container OS details?

---

<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:** [September 26, 2022, 5:32pm UTC](https://discuss.elastic.co/t/wrong-host-system-info-from-containerized-elastic-agent/313190/2 "2022-09-26T17:32:58Z")

</div>

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