Tilemap manifest loading in 5.2 blocks loading of Kibana for up to 60s when behind a firewall

[magicmicah]

Upon initial loading of Kibana, the page takes approximately one minute to load. Using dev tools, the page hangs due to trying to load this URL:

https://tiles.elastic.co/v2/manifest?my_app_version=5.2.0

We are in a firewalled environment and have no need for tilemaps service. I checked to see if there is a way to disable tilemaps but do not see one. As a workaround we modified this JS script and the initial page loads much quicker:

Modified this file: /usr/share/kibana/src/server/config/schema.js

Changed to below:
manifestServiceUrl: _joi2['default'].string()['default']('http://localhost/'),
From this:
manifestServiceUrl: _joi2['default'].string()['default']('https://tiles.elastic.co/v2/manifest'),
Apologies if there is an answer or it's listed in the documentation but I did not see it unfortunately. Thank you in advance.

[epixa]

@thomasneirynck I thought we were only requesting the manifest when a tilemap is on the screen?

[thomasneirynck]

@epixa, you are correct. That should be the behavior but it isn't.

@magruder85 this is a bug and we need to resolve this. When you are not using the tilemap visualization, Kibana should not phone home to the server. Please stay tuned, I'll update you when a fix is in place.

[magicmicah]

I will stay tuned. :) Thank you.

[epixa]

@magruder85 As an immediate workaround, if you configure any third party tile service, we won't attempt to load the manifest.

[thomasneirynck]

thanks @epixa.

@magruder85: @epixa refers to the tilemap.url parameter in config/kibana.yml. Set it to a 3rd party service. For example:
tilemap.url: http://example.com/service/{z}/{y}/{x}.png

[thomasneirynck]

Note that when plugging in your own tile-service (as suggested here #10205 (comment) by @landong1973 ), be sure its use is approved by the TMS-provider. (we learned this the hard way when MapQuest shut down its tile-service).