Reputation: 1036
Currently I use azure maps fuzzy search ( https://learn.microsoft.com/en-us/rest/api/maps/search/getsearchfuzzy )
So when I do a search using GET https://atlas.microsoft.com/search/fuzzy/json?subscription-key={subscription-key}&api-version=1.0&query=1600 Pennsylvania ave Washington DC 20500 I get several results, including POI and Point Address.
This event is triggered off of an onblur event from an address change.
Last month we got billed for 5,000,000 hits from Azure when we didn't have near that many. That number should have been closer to 6000.
Is that because I am using the fuzzy search or what? I can't seem to find any information on why our hits would have been so high.
Upvotes: 0
Views: 277
Reputation: 316
The delta seems absurdly high (6000 vs 5,000,000). Are all those 5,000,000 calls, Search Fuzzy API calls?
Can't say much without looking at the actual code but if the behavior is that in your app the "user adds an address in a form field" and when the "user finishes adding the address and clicks outside that address box (onBlur event fires)" and calls Azure Maps Search Fuzzy API - that would be one call (irrespective of it returning multiple/different categories of addresses POIs, Point Addresses etc.) - [Unless you are using the API in the "predictive" mode (param typeahead = true) and calling the API everytime the user enters a character]
I would try and check the number of calls going out to Azure Maps using any network capture tool (Fiddler/Browser n/w capture) and if they look okay then check the Azure Maps metrics for "Search Fuzzy API" in the Azure Portal to see if they look ok.
But if you are only making an explicit call to the API manually once the user finishes adding/editing the address then I don't see a reason why that call won't be recorded as 1 call on the Azure Maps side.
Upvotes: 1