# HTTP Monitoring Liveness not activateable via Fleet **URL:** \ **Category:** Elastic Agent\ **Tags:** elastic-stack-monitoring\ **Created:** [August 26, 2024, 8:54am UTC](https://discuss.elastic.co/t/http-monitoring-liveness-not-activateable-via-fleet/365539 "2024-08-26T08:54:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Alphayeeeet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alphayeeeet/32/126382_2.png) [@Alphayeeeet](https://discuss.elastic.co/u/Alphayeeeet)\ **Post date:** [August 26, 2024, 8:54am UTC](https://discuss.elastic.co/t/http-monitoring-liveness-not-activateable-via-fleet/365539/1 "2024-08-26T08:54:50Z")
After the new HTTP monitoring is configurable in the Fleet agent policy since 8.15. We wanted to use that for liveness/readiness probes in Kubernetes. However even if the ports are configured in the fleet agent policy. The HTTP monitoring is not enabled according to diagnostics (the /liveness endpoint in more detail). When trying to enable the endpoint via custom agent.yml and mounting that via ConfigMap it is still disabled. This is the mentioned part in the local-config.yml in the diagnostics: ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/6/c67832efcf3cb0140c786d70b4ba8d9dfad47a42.png) Any advice is appreciated, on how to enable this. ---
**Author:** ![Alphayeeeet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alphayeeeet/32/126382_2.png) [@Alphayeeeet](https://discuss.elastic.co/u/Alphayeeeet)\ **Post date:** [August 26, 2024, 8:59am UTC](https://discuss.elastic.co/t/http-monitoring-liveness-not-activateable-via-fleet/365539/2 "2024-08-26T08:59:34Z")
Found this PR: [[Fleet] Add toggles for `agent.monitoring.http.enabled` and `agent.monitoring.http.buffer.enabled` to agent policy advanced settings by kpollich · Pull Request #190984 · elastic/kibana · GitHub](https://github.com/elastic/kibana/pull/190984) Why was this disabled in the first try. In that way it isn't even supposed to work in any way or am I wrong?