# 'logging-and-metrics' system owned cluster unhealthy with Kibana instance deployment failing **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [November 17, 2021, 9:02pm UTC](https://discuss.elastic.co/t/logging-and-metrics-system-owned-cluster-unhealthy-with-kibana-instance-deployment-failing/289505 "2021-11-17T21:02:36Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![A\_I](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_i/32/78726_2.png) [@A\_I](https://discuss.elastic.co/u/A_I)\ **Post date:** [November 17, 2021, 9:02pm UTC](https://discuss.elastic.co/t/logging-and-metrics-system-owned-cluster-unhealthy-with-kibana-instance-deployment-failing/289505/1 "2021-11-17T21:02:36Z")
I am unfortunately not able to provide logs at this time however guidance on a starting point would be helpful. We recently needed to increase the capacity of our logging-and-metrics cluster, the advice was to change `system_owned:` to `false` and then increase the capacity as necessary in the advanced edit section. Elasticsearch came back healthy but Kibana came back unhealthy, we decided to delete the instance and redeploy it. Ever since then we have not been able to recover Kibana and would just like some guidance as to where we could start debugging. Am I able to use the Elasticsearch API to access the logs for the 'logging-and-metrics' cluster? & Is there a way to redeploy a system cluster entirely? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 1, 2021, 9:03pm UTC](https://discuss.elastic.co/t/logging-and-metrics-system-owned-cluster-unhealthy-with-kibana-instance-deployment-failing/289505/2 "2021-12-01T21:03:09Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.