Documentation of Kibana configuration not completely correct?

[heidivanparys]

I tried to follow the instructions on https://github.com/geonetwork/core-geonetwork/blob/86c8dc5eb5e1a272e13144fb644f80384d5c7797/es/es-dashboards/README.md. I have Elasticsearch, Kibana and GeoNetwork up and running.

However, I cannot reproduce what is written on

core-geonetwork/es/es-dashboards/README.md

Lines 62 to 73 in 86c8dc5

	1. Kibana should be running from:
	```
	http://localhost:5601
	```
	2. And should be visible within the geonetwork interface at:
	```
	http://localhost:8080/geonetwork/dashboards
	```

When I use the following configuration:

server.basePath: "/geonetwork/dashboards"
server.rewriteBasePath: false

then I can access http://localhost:8080/geonetwork/dashboards successfully, both directly and from within the admin console in the GeoNetwork web application. But I cannot access http://localhost:5601 successfully, I get an 404 error.

And when I use the following configuration:

server.basePath: ""
server.rewriteBasePath: false

then I can access http://localhost:5601 successfully, but I cannot access http://localhost:8080/geonetwork/dashboards successfully, I get an 404 error.

Is it possible that the documentation is out of date, and that only one of the URLs can be resolved successfully? I assume that the idea is that http://localhost:8080/geonetwork/dashboards should work fine, so it can be accessed from within GeoNetwork?

[josegar74]

When you change the server.basePath to /geonetwork/dashboards, Kibana is accessible at http://localhost:8080/geonetwork/dashboards .

I think the documentation should be updated to something like this, to be more clear:

1. Kibana should be running on port 5601
2. And should be visible within the geonetwork interface at:

   http://localhost:8080/geonetwork/dashboards 
   

Or even remove the item about the Kibana port as seems no much relevant for this.

[heidivanparys]

According to https://elastic.aiops.work/guide/en/kibana/8.14/access.html, the status can be checked using http://localhost:5601/api/status, and that worked indeed. I updated #9135 to add that information in the README.md file.