# Adding Memcached integration turns agent unhealthy **URL:** \ **Category:** Elastic Agent\ **Created:** [February 10, 2023, 11:39am UTC](https://discuss.elastic.co/t/adding-memcached-integration-turns-agent-unhealthy/325254 "2023-02-10T11:39:29Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![rrodrigues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rrodrigues/32/117106_2.png) [@rrodrigues](https://discuss.elastic.co/u/rrodrigues)\ **Post date:** [February 10, 2023, 11:39am UTC](https://discuss.elastic.co/t/adding-memcached-integration-turns-agent-unhealthy/325254/1 "2023-02-10T11:39:29Z")
When I add the Memcached Elastic Agent integration to a Fleet-managed agent it goes unhealthy. I believe this issue is similar to [this one](https://github.com/elastic/elastic-agent/issues/1822) reported on Nginx/Kafka integration. Elastic Cloud/Elastic Agent: 8.6.1 Memcached integration: 0.3.0 OS: Ubuntu 20.04 aarch64 Memcached: 1.6.18 Logs: ```auto [elastic_agent][error] Spawned new component memcached/metrics-7bf238f0-a808-11ed-a884-99a98f944e1f: input not supported [elastic_agent][error] Spawned new unit memcached/metrics-7bf238f0-a808-11ed-a884-99a98f944e1f-memcached/metrics-memcached-863ed670-0d9e-4d45-b945-a550ecc9cd3c: input not supported [elastic_agent][error] Spawned new unit memcached/metrics-7bf238f0-a808-11ed-a884-99a98f944e1f: input not supported ``` Anyone else having the same problem? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 10, 2023, 11:40am UTC](https://discuss.elastic.co/t/adding-memcached-integration-turns-agent-unhealthy/325254/2 "2023-03-10T11:40:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.