# Computers with no data in metrics inventory **URL:** \ **Category:** Elastic Observability\ **Created:** [October 15, 2020, 5:20pm UTC](https://discuss.elastic.co/t/computers-with-no-data-in-metrics-inventory/252246 "2020-10-15T17:20:04Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![0xDECAFBAD](https://avatars.discourse-cdn.com/v4/letter/0/e47c2d/32.png) [@0xDECAFBAD](https://discuss.elastic.co/u/0xDECAFBAD)\ **Post date:** [October 15, 2020, 5:20pm UTC](https://discuss.elastic.co/t/computers-with-no-data-in-metrics-inventory/252246/1 "2020-10-15T17:20:04Z")
I have a couple computers that used to have the Elastic Agent installed and reporting metric data. Now that they are no longer reporting metric data they still show up on the metric inventory screen in Kibana showing 0% CPU usage. If I go to host metrics it says there is no data to display. Why would they still be showing up on the inventory page if there is no data? ---
**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\ **Post date:** [October 26, 2020, 5:01pm UTC](https://discuss.elastic.co/t/computers-with-no-data-in-metrics-inventory/252246/2 "2020-10-26T17:01:10Z")
Hi @0xDECAFBAD, AFAIK the nodes on the inventory page are collected from a wider time range. Could that be the reason why they stay around for longer? ---
**Author:** ![0xDECAFBAD](https://avatars.discourse-cdn.com/v4/letter/0/e47c2d/32.png) [@0xDECAFBAD](https://discuss.elastic.co/u/0xDECAFBAD)\ **Post date:** [October 26, 2020, 6:51pm UTC](https://discuss.elastic.co/t/computers-with-no-data-in-metrics-inventory/252246/3 "2020-10-26T18:51:38Z")
Possibly? It's throwing three computers that have the "Desktop" fleet configuration I created in along with computers that have the "Server" fleet configuration. The server configuration collects performance metrics while the desktop config does not, hence the 0% CPU usage for those hosts and no data when I hover over the host. The rest of the hosts that have the "Desktop" config applied do not show up in inventory. ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/f/0f7e4574d84829a8586662a37def89737a4f770f.png) ---
**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\ **Post date:** [October 26, 2020, 7:05pm UTC](https://discuss.elastic.co/t/computers-with-no-data-in-metrics-inventory/252246/4 "2020-10-26T19:05:46Z")
Interesting... do you happen to collect logs into a `logs-*` or `filebeat-*` index from the three 0% desktop machines? ---
**Author:** ![0xDECAFBAD](https://avatars.discourse-cdn.com/v4/letter/0/e47c2d/32.png) [@0xDECAFBAD](https://discuss.elastic.co/u/0xDECAFBAD)\ **Post date:** [October 26, 2020, 8:51pm UTC](https://discuss.elastic.co/t/computers-with-no-data-in-metrics-inventory/252246/5 "2020-10-26T20:51:54Z")
I'm not sure. I'm new to Elastic and just recently spun up a self managed deployment. It should be whatever the 7.9 Elastic Agent defaults to. I think I might have initially had the System, Windows, and Endpoint integrations on that configuration and then I dropped it down to just Endpoint. I'm guessing that is part of the cause. Those might have been the three machines that were on the original configuration before I removed the System and Windows integrations. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 8:15am UTC](https://discuss.elastic.co/t/computers-with-no-data-in-metrics-inventory/252246/6 "2022-11-04T08:15:30Z")