Kibana: X-Pack Basic license, maps not zooming beyond level 10

[asp-sterling]

Kibana version: 5.6.3
Elasticsearch version: 5.6.3
Server OS version: CentOS 7.4.1708
Browser version: Edge, Firefox 56.0 (64-bit)
Browser OS version: Windows 10
Original install method (e.g. download page, yum, from source, etc.): yum
Description of the problem including expected versus actual behavior: After applying the X-Pack Basic license, maps stopped zooming beyond level 10 (button greyed out). Prior to that, while licensed as trial, everything worked normally. Other Basic license features are still working as expected (Monitoring, Search Profiler, Grok Debugger...). Tried restarting the Kibana service and rebooting the server, but to no avail.

[leandrojmp]

I'm having the same problem, when I reach zoom level 10 the zoom button is greyed out, I'm also using the basic license of X-Pack and the other features works fine.

[thomasneirynck]

I see this was asked on discuss as well. https://discuss.elastic.co/t/tile-map-zoom-level-does-not-change-even-with-basic-license/104706. I will check into it and update on status here as soon as we know more. thx all

[thomasneirynck]

I cannot reproduce this in 5.6.3:

I pasted a screenshot here of what the map should look like:

---

Can you double check the following things?

1) When you check the ES-license, do you see a basic-license type?

e.g. try requesting (update username/password appropriately)

> curl http://elastic:changeme@localhost:9200/_xpack/license
{
  "license" : {
    "status" : "active",
    "uid" : "foobarfoobar",
    "type" : "basic",
    "issue_date" : "2017-06-21T00:00:00.000Z",
    "issue_date_in_millis" : 1498003200000,
    "expiry_date" : "2018-01-30T23:59:59.999Z",
    "expiry_date_in_millis" : 1517356799999,
    "max_nodes" : 100,
    "issued_to" : "foobar",
    "issuer" : "foobar",
    "start_date_in_millis" : 1498003200000
  }
}

2) When you open the browser debugger (in Chrome, this would be Ctrl-Shft-J), and check the network tab, you should find a call to a metadata-service.

Something like:
https://tiles.maps.elastic.co/v2/manifest?my_app_version=5.6.3&license=foobarfoobar

This returns a JSON-object with min/max properties. It should say 0-18.

{  
   "services":[  
      {  
         "id":"road_map",
         "url":"https://tiles.maps.elastic.co/v2/default/{z}/{x}/{y}.png?elastic_tile_service_tos=agree&my_app_name=kibana",
         "minZoom":0,
         "maxZoom":18,
         "attribution":"© [OpenStreetMap](http://www.openstreetmap.org/copyright) contributors | [Elastic Maps Service](https://www.elastic.co/elastic-maps-service)"
      }
   ],
   "license-id":"foobarfoobar"
}

[rashmivkulkarni]

Installed and brought up the stack with basic license on released 5.6.3 I do see the zoom level do show upto 18. Cannot reproduce it on my end. ( tried it on Chrome , Ubuntu 64 bit machine)

[leandrojmp]

Sorry, I didn't mentioned the version here, only in discuss. I'm running version 5.6.2.

I double checked and I can see the license type installed as the basic license, below is the curl result (with the license uid and issued to changed):

{
  "license" : {
    "status" : "active",
    "uid" : "MY-LICENSE-UID",
    "type" : "basic",
    "issue_date" : "2017-09-21T00:00:00.000Z",
    "issue_date_in_millis" : 1505952000000,
    "expiry_date" : "2018-09-21T23:59:59.999Z",
    "expiry_date_in_millis" : 1537574399999,
    "max_nodes" : 100,
    "issued_to" : "LICENSE ISSUED TO",
    "issuer" : "Web Form",
    "start_date_in_millis" : 1505952000000
  }
}

And using the chrome debugger it calls the tile service but says that the maxZoom is 10.

{
"services":[
        {"id":"road_map",
         "url":"https://tiles.maps.elastic.co/v2/default/{z}/{x}/{y}.png?elastic_tile_service_tos=agree&my_app_name=kibana",
         "minZoom":0,
         "maxZoom":10,
         "attribution":"© [OpenStreetMap](http://www.openstreetmap.org/copyright) contributors | [Elastic Maps Service](https://www.elastic.co/elastic-maps-service)"
        }],
        "license-id":"MY-LICENSE-UID"
}

[thomasneirynck]

@leandrojmp can you double check if the web-request to the tiles-manifest in the Chrome debugger includes your license-id as a query-parameter?

it should look something like:
https://tiles.maps.elastic.co/v2/manifest?my_app_version=5.6.3&license=MY-LICENSE-ID

[leandrojmp]

Yes, the license is a query parameter as show in the print below.

[thomasneirynck]

ok, so I tested this on 5.6.2, and cannot reproduce this either:

Perhaps this is related to your particular license, I'm not an expert on the licensing, but I'll ask around, please stay tuned.

[thomasneirynck]

@leandrojmp what version of the stack did you upgrade from prior to this?

[thomasneirynck]

Ok, I can repro this. I generated a brand new license from the website using https://register.elastic.co/registration (so not my test license) and I get the same issue.

We're looking into this, plz stay tuned.

[leandrojmp]

@thomasneirynck it's a brand new install on production, I started with 5.6.1, installed x-pack and the license and a few days laters I updated to 5.6.2, last week I started to configure the geo_point fields in my index and saw this problem.

[drewr]

We tracked this back to an issue with the contract between the maps service and the licensing portal. Will get a fix out this week.

[leandrojmp]

Is this issue fixed? What do I need to do? Request a new basic license in the licensing portal?

[drewr]

Thanks for asking @leandrojmp, we hit a few complications and are still working on it. Will update when we have a better estimate.

[drewr]

We've deployed a fix for this issue. @asp-sterling @leandrojmp please check it again at your convenience.

[asp-sterling]

Works great now, thanks! :)

[leandrojmp]

It's working for me too, thanks!

[thomasneirynck]

thanks :100: @drewr!

[luckydonald]

I get this same issue with version 6.2.4.
GET /_xpack/license

{
  "license": {
    "status": "active",
    "uid": "REDACTED",
    "type": "basic",
    "issue_date": "2018-05-04T00:00:00.000Z",
    "issue_date_in_millis": 1525392000000,
    "expiry_date": "2019-05-04T23:59:59.999Z",
    "expiry_date_in_millis": 1557014399999,
    "max_nodes": 100,
    "issued_to": "REDACTED",
    "issuer": "Web Form",
    "start_date_in_millis": 1525392000000
  }
}

Version:
GET /

{
  "name": "REDACTED",
  "cluster_name": "elasticsearch",
  "cluster_uuid": "REDACTED",
  "version": {
    "number": "6.2.4",
    "build_hash": "ccec39f",
    "build_date": "2018-04-12T20:37:28.497551Z",
    "build_snapshot": false,
    "lucene_version": "7.2.1",
    "minimum_wire_compatibility_version": "5.6.0",
    "minimum_index_compatibility_version": "5.0.0"
  },
  "tagline": "You Know, for Search"
}

server:tileprox/20171031230139-9bbba72
status:200
x-proxy-backend:71297bfd7fc2
x-request-id:771f447eec0246fc9b09b7af89f41a7c

[thomasneirynck]

let's continue discussion on that new issue https://github.com/elastic/kibana/issues/19017.