Nagios Support Forum

I'm sure others may be reporting it soon. Looks like mapquest has disabled direct access to the tiles.

http://devblog.mapquest.com/2016/06/15/ ... le-access/

Are there any plans to provide support for the new format, and allow users to use free API keys?

Thank you for bringing this to our attention. I will make the developers aware tomorrow when we are in the office, and decide how to proceed.

It's still working for us.

eloyd wrote:It's still working for us.

It seems to be hit & miss, presumably being rolled out gradually? We first noticed it on my coworker's system when opening up a new dashboard, while it kept working on mine. Took the working system home, reloaded one of the dashboards, and it showed the errors.

For example this morning I opened one of the dashboards, it worked. Changed the query from a wildcard to be more specific, and the map showed this error. So perhaps it may be related to the scale? Zooming out started to show some tiles as maps, and some as the error. Attached is a sample.

I'm also affected by this issue. I've brought it up to the developers.

This is an issue with how Kibana accesses these maps. It must have been done via a publicly accessible API and apparently MapQuest is not a big fan of that. It's an issue with ALL Kibana versions and they are looking into solutions right now. Unfortunately there isn't much we can do, though it looks like there is going to be some way to sign up an account or something. We will have to let you know more details as we get them.

The "simple" solution (easy for me to say, make Scott/Bryan do it) is to have end users enter their own AppKey information and pass that on to MapQuest. Or switch to Google Maps and be done with it (and throw a bunch of additional information into Google's pile of information).

I find it interesting that the MapQuest error message (which we are now also seeing) is using Google's URL shortener. Presumably, Google's mapping and geolocation services are MapQuest's main competition.

I filed a bug report for this, ID #9074. I requested that an option be added to specify which API URL to use for the Bettermap lookups.

The "simple" solution (easy for me to say, make Scott/Bryan do it) is to have end users enter their own AppKey information and pass that on to MapQuest. Or switch to Google Maps and be done with it (and throw a bunch of additional information into Google's pile of information).

It's hard to say -- we also have to look into licensing for it so it may not just be that 'simple'.

I posted an announcement in customer support, and can post one in here too but the way the Google Maps API and, say, the MapQuest API works we may have to change the plugin a lot. We are looking into possible solutions to the issue and will release a new version of NLS with the fixes once it's implemented since we cannot use the fix the kibana implemented due to restrictions on the elastic tile server TOS.

Update on this. We have a fix for now that will be implemented with a 1.4.2 version, which will come out by the end of the week.