- Kibana Guide: other versions:
- Introduction
- Get started
- Set Up Kibana
- Discover
- Visualize
- Creating a Visualization
- Saving Visualizations
- Using rolled up data in a visualization
- Line, Area, and Bar charts
- Controls Visualization
- Data Table
- Markdown Widget
- Metric
- Goal and Gauge
- Pie Charts
- Coordinate Maps
- Region Maps
- Timelion
- TSVB
- Tag Clouds
- Heatmap Chart
- Vega Graphs
- Inspecting Visualizations
- Dashboard
- Canvas
- Graph data connections
- Machine learning
- Elastic Maps
- Code
- Infrastructure
- Logs
- APM
- Uptime
- SIEM
- Dev Tools
- Stack Monitoring
- Management
- Reporting from Kibana
- REST API
- Kibana plugins
- Limitations
- Release Highlights
- Breaking Changes
- Release Notes
- Developer guide
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Upgrade Readiness Status
editUpgrade Readiness Status
editThis API is experimental and may be changed or removed completely in a future release. The underlying Upgrade Assistant concepts are stable, but the APIs for managing Upgrade Assistant are currently experimental.
Request
editTo check the status of your cluster, submit a GET request to the /api/upgrade_assistant/status
endpoint:
Note: You cannot access this endpoint via the Console in Kibana.
GET /api/upgrade_assistant/status
Response
editA successful call returns a response code of 200
and a response body
containing a JSON structure similar to the following example:
{ "readyForUpgrade": false, "cluster": [ { "message": "Cluster deprecated issue", "details": "...", "level": "warning", "url": "https://docs.elastic.co/..." } ], "indices": [ { "message": "Index was created before 6.0", "details": "...", "index": "myIndex", "level": "critical", "reindex": true, "url": "https://docs.elastic.co/..." } ] }
You can fix indices with the |
Was this helpful?
Thank you for your feedback.