---
title: Check Kibana server status
description: The status page displays information about the server resource usage and installed plugins. It only reports for the individual responding Kibana instance...
url: https://www.elastic.co/elastic/docs-builder/docs/3028/troubleshoot/kibana/access
products:
  - Kibana
applies_to:
  - Elastic Stack: Generally available
---

# Check Kibana server status
The status page displays information about the server resource usage and installed plugins. It only reports for the individual responding Kibana instance.
To view Kibana's status, use the `status` endpoint. For example, `localhost:5601/status`.
![Kibana server status page](https://www.elastic.co/elastic/docs-builder/docs/3028/troubleshoot/images/kibana-kibana-status-page-7_14_0.png)

For JSON-formatted server status details, use the [Kibana current status API](https://www.elastic.co/docs/api/doc/kibana/v9/operation/operation-get-status). For example, `localhost:5601/api/status`.

## Triage Kibana health using the status API

The following steps demonstrate a typical investigative flow. It assumes the [Kibana current status API](https://www.elastic.co/docs/api/doc/kibana/v9/operation/operation-get-status) is saved locally as `kibana_status.json`, and uses third-party tool [JQ](https://jqlang.github.io/jq/) as a JSON processor.
1. Check the overall status.
   The UI will report "Kibana status is" and then the status. You can see this in the API output by running the following command:
   ```bash
   cat kibana_status.json | jq '{ overall: .status.overall.level }'
   ```
2. Check the core plugins.
   The UI includes a **Plugin status** table with a list of plugins. IDs for core plugins use a prefix of `core`.
   You can check these in the API output by running the following command:
   ```bash
   cat kibana_status.json | jq -r '.status.core|{ elasticsearch: .elasticsearch.level, savedObjects: .savedObjects.level }'
   ```
   Before you review any further plugins, check that the `elasticsearch` and `savedObjects` are healthy and resolve any issues:
   - If the connection to Elasticsearch is unhealthy, refer to [Error: Kibana server is not ready yet](https://www.elastic.co/elastic/docs-builder/docs/3028/troubleshoot/kibana/error-server-not-ready).
- If the connection to Saved Objects is unhealthy, refer to [Troubleshoot Kibana migration and upgrades](https://www.elastic.co/elastic/docs-builder/docs/3028/troubleshoot/kibana/migration-failures).
3. Check non-core plugins.
   The UI **Plugin Status** list reports the status of the other plugins running on the instance. Plugins can be dependent upon each other. You should first check the health of the common underlying plugins: `alerting`, `reporting`, `ruleRegistry`, `savedObjects`, `security`, and `taskManager`.
   You can check these in the API output by running the following command:
   ```bash
   cat kibana_status.json | jq -rc '.status.plugins|to_entries[]|select(.key=="taskManager" or .key=="savedObjects" or .key=="security" or .key=="reporting" or .key=="ruleRegistry" or .key=="alerting") |{plugin:.key, status:.value.level, reason:.value.summary}'
   ```
   For an example of a degraded Task Manager and how that degradation cascades into other plugins, refer to [Troubleshooting Kibana health](https://www.elastic.co/blog/troubleshooting-kibana-health#check-dependencies). For more information on investigating a degraded Task Manager, refer to [Troubleshoot Kibana Task Manager](https://www.elastic.co/elastic/docs-builder/docs/3028/troubleshoot/kibana/task-manager).


## Next steps

For a deeper troubleshooting walkthrough, refer to our Troubleshooting Kibana health [blog](https://www.elastic.co/blog/troubleshooting-kibana-health) and [video](https://www.youtube.com/watch?v=AlgGYcpGvOA&list=PL_mJOmq4zsHbQlfEMEh_30_LuV_hZp-3d&index=28).