[Beats 7.12.1] Workaround for error while loading dashboards "Exiting: Kibana API is not available in Kibana version 1.0.0"
See original GitHub issueI set up Metricbeat 7.12.1 with the version work-around in OpenSearch. However I did not see anything similar regarding the version check against OpenSearch Dashboards. So I get this:
% metricbeat setup
Overwriting ILM policy is disabled. Set `setup.ilm.overwrite: true` for enabling.
Index setup finished.
Loading dashboards (Kibana must be running and reachable)
Exiting: Kibana API is not available in Kibana version 1.0.0
I bet I could load the dashboards manually into OpenSearch Dashboards which is what I am going to try next. However of course it would be nice to have it just work out of the box.
This is with OpenSearch 1.0.0 installed as tarball.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:24 (3 by maintainers)
Top Results From Across the Web
Configure Kibana dashboard loading | Filebeat Reference [8.5]
If Kibana is not available at startup, Filebeat will stop with an error. To enable dashboard loading, add the following setting to the...
Read more >OpenSearch VS ElasticSearch - ElectricBrain
You may not use the licensed work to provide an "Elasticsearch/Kibana as a ... Kibana API is not available in Kibana version 1.0.0...
Read more >How To Install Elasticsearch, Logstash, and Kibana (Elastic ...
In this tutorial, we will go over the installation of the Elastic Stack on an Ubuntu 22.04 server. You will learn how to...
Read more >https://raw.githubusercontent.com/elastic/beats/ma...
Please note that you cannot load templates into Elasticsearch 7.8 or older with this ... Fix memory leak in SQL module when database...
Read more >Frequently Asked Questions - OpenSearch
We bring years of experience working with Elasticsearch and Kibana ... No. There is documentation on which versions of Logstash and Beats work...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@electricbrain-code I just saw your article - it’s an incredibly good write up of the problem with metricbeats described in this issue https://www.electricbrain.com.au/pages/analytics/opensearch-vs-elasticsearch.php
Further to my recent post, I have succeeded in finding how metricbeat know the kibana/opensearch-dashboards API version:
curl -u admin:admin -XGET -H ‘Content-Type: application/json’ http://localhost:5601/api/status
This api url is in the go source file.
Lots of JSON comes back at you. Stuff like (note: “number”:“1.0.0” is the offending piece) : { “name”: “42f975ee9b4f”, “uuid”: “9bb7854c-ae61-4509-a4f6-e23f8be61e38”, “version”: { “number”: “1.0.0”, “build_hash”: “b15ad258e6960003e609a70889cda5fb39f90947”, “build_number”: 36473, “build_snapshot”: false }, “status”: { “overall”: { “since”: “2021-08-09T06:43:30.711Z”, “state”: “green”, “title”: “Green”, “nickname”: “Looking good”, “icon”: “success”, “uiColor”: “secondary” }, “statuses”: [ { “id”: “core:opensearch@1.0.0”, “message”: “OpenSearch is available”, “since”: “2021-08-09T06:43:30.711Z”, “state”: “green”, “icon”: “success”, “uiColor”: “secondary” }, etc, etc, etc, lots of etc’s