Tell us what you are trying to do?
I installed maps and obtained an azure maps key.
I added a maps field to some of my post types, and then proceeded to add addresses and do address lookups for 168 posts to get the co-ordinates - manually. This is all I have done. I've not even added the maps field to a display template. A few days later, I received an email from Azure, informing me that I have used up my $200 free allowance, and according to them, I have done around 500K lookups. They are adamant that this is correct.
I am the only person using this website, as it is still in development, so where on earth have these lookups come from
One comment I will make, is that quite often when I'm editing posts (which incidentally do NOT have the maps field assigned to them) in admin, I see a message 'waiting for microsoft atlas' or something to that effect
Is there any documentation that you are following?
the instructions for setting up the azure account
Is there a similar example that we can see?
all there is, is the addresses in the few posts where I have done the lookups.
What is the link to your site? staging.uniqwin.co.uk
Hello and thank you for contacting the Toolset support.
Toolset Maps plugin uses a table on the database to store the results of lookup calls to Azure API. MySQL should be at least 5.6 for the geolocation capabilities.
I am not sure what has generated all these calls to Azure, and you may be right, calls were done from posts that do not have an address yet, but we'll need to be sure.
I wonder if the Azure support team could get you logs of when the calls were done or what data was sent on these calls. That way we can check if it was called from those posts and we can try to reproduce this on a clean install.
It was trying to access atlas.microsoft.com for posts that DON'T have the maps fields included (i.e. it is not an option for the post type)
They aren't particularly helpful. I can forward the case information to you if you wish to pursue that with them. We are talking about the 21st Sept
I have removed the azure key from my installation now, and everything is a whole lot faster!
We, at support, won't be able to communicate with the Azure team. If we find a bug that is related to the Azure platform, we'll escalate it to our developers and they may make contact if needed.
Let me know if there is anything else we can do to help here.
I have asked them for the logs a couple of days ago, so I suggest you wait a minute before closing this. I think it is in your interest to establish what the problem is, because it certainly not something I've done
Sure, we'll keep this ticket open and we'll do our best to help you and to find any possible bug/error on our plugins that might have caused this.
I'll set this ticket as waiting for your reply, which should keep it open for 3 weeks. And you will receive automatic notifications before it is being closed. In that case, just reply here so we can extend it for another 3 weeks.
I have had the following information from AZURE:
There were 99310 requests and 99305 of them are the same query on:
search/fuzzy/json:
/?api-version=1.0&query=0.000000,%200.000000&idxSet=Geo&limit=1&lat=0.000000&lon=0.000000&radius=1000&subscription-key=***
They all came from hidden link.
All these requests were made in this 2 minutes window between 07:02:23 PCT and 07:04:27 PCT on September 29th. 71613 of them succeeded.
does this mean anything to you? This was about a week after activating maps. I don't believe I have anything else that will use the interface
I searched for any use of the Azure Fuzzy Search on the code source of our plugins and I could not find any. So, I suspect, that another component on your website is probably the one who's making these calls.
Can you please paste your Toolset Debug information in the Debug information field, so we can know what themes and plugins you are using?
- https://toolset.com/faq/provide-debug-information-faster-support/
In the meantime, I'll check with our 2nd Tier to confirm if we have something that should call the Fuzzy Search endpoint.
Please note that I have deactivated Maps
Thank you!
Your current MySQL 5.5.5 does not offer geolocation capabilities. Check this screenshot hidden link
This means, that Toolset will not be able to create the location data cache table. This means:
- Each view that displays location data will perform an API call to the Azure platform for each post/marker.
- You won't be able to perform geolocation search queries, such as distance search.
Please check our requirement page, we need, at least MySQL 5.6 https://toolset.com/toolset-requirements/
Reply from my server support people:
Your server is running MariaDB 10.1 which is roughly equivalent to MySQL 5.7. If you're running into issues, can you let us know specifically what it says is missing?
Can you share the debug information again, in your next private reply? Just copy/paste it in your next reply, no need to enter any credentials.
According to our Toolset Maps developers, Toolset Maps would not perform any fuzzy search requests to the Azure platform.
I have now received the activity log from MS Azure Support. What is the best way to get this to you? it's about 3Mb
MariaDB has also been updated to 10.5 today
As far as access to the website is concerned, this is a production website, plus MAPS was disabled because of the issue. This also resolved the issue of 'waiting for compass' or similar when editing posts.
I don't know if this is relevant, but the post type where the geo location data is included (and it is purely for SEO schema purposes), was at the time also the parent of 2 relationships, with each child post type having several thousand instances. This has all been disabled for the time being, to focus on launching the updates that were done. We're also using admin columns pro and this is set to display the the geo location.
I will have some more posts to do geo-location for, so it would be useful to get it resolved. However, I might opt for Google this time.
I set your next reply to be private to let you share a download link of the logs. Please use a sharing service such as Google Drive or DropBox.
According to our Toolset Maps developers, we do not perform any fuzzy search requests(endpoint search/fuzzy/json), I would suspect that "Admin Columns" was, probably, performing these requests in order to display the result in the geolocation column.
I do not think that the post type's relationships can be involved in this issue. But, I would like to know what do you mean by "This also resolved the issue of 'waiting for compass' or similar when editing posts"
