Status Update
Comments
st...@gmail.com <st...@gmail.com> #2
cr...@gmail.com <cr...@gmail.com> #3
vi...@google.com <vi...@google.com> #4
Dear developers, we have now rolled out the change for the following APIs:
- Elevation API
- Maps Static API
- Street View Static API
- Time Zone API
Please see the updated issue description in
We will post further updates as the rollout extends to Directions API, Geocoding API and Places API.
Note: A small fraction of our customers on these remaining three APIs may start to see a significant percentage of their requests being reported as
404
s. This is not an automatic signal of any Google Maps Platform issue, (see the notes about determining the baseline-ratio for404
responses in your application in). comment #1 Especially if your
404
ratio remains exceedingly high and fairly stable over an extended period of time, it is likely a symptom of some kind of systemic issue in your application logic or the data you pass to the Google Maps Platform APIs. Therefore, before reaching out to support, we kindly ask you to do the following
Determine what your historical
404
baseline-ratio is.Collect samples of requests that result in
ZERO_RESULTS
,NOT_FOUND
andDATA_NOT_AVAILABLE
responses, and validate that the queries look semantically correct for the API in question: e.g., addresses are correctly formatted for your country, location coordinates are on land, or Directions API requests haveorigin
s anddestination
s that are physically reachable by the supported travel modes.If the queries look correct, and the ratio or
404
s has increased drastically, don't hesitate to reach out to support with the examples you collected.
vi...@google.com <vi...@google.com> #5
We are now rolling our the monitoring metric improvements on the Geocoding API. During this week, you should start to see a gradual shift from 200
to 404
for ZERO_RESULTS
traffic on this API.
sh...@gmail.com <sh...@gmail.com> #6
Ok
vi...@google.com <vi...@google.com> #7
We will now be rolling out the monitoring metric improvements on the Directions API and Places API. Over this week you should start to see a gradual shift from 200
to 404
for ZERO_RESULTS
and NOT_FOUND
traffic on these APIs.
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #8
Dear developers, contrary to our original plans, the Places API change didn't make its way into production until earlier this week due to our holiday production freeze. Apologies for any inconvenience!
do...@gmail.com <do...@gmail.com> #9
vi...@google.com <vi...@google.com> #10
Hi, please reach out to our tech support team as described
You can also find the instructions in (Brazilian) Portuguese here:
Description
Dear Google Maps Platform Developers,
TL;DR: We are changing the way error codes are reported in our monitoring. If you do not consume Google Cloud Monitoring metrics for Google Maps Platform services, you can ignore this public issue.
What is happening?
To give you more insights into maps or serviceruntime monitoring metrics across all our APIs.
DATA_NOT_AVAILABLE
,NOT_FOUND
andZERO_RESULTS
responses across the Google Maps Platform service, we are unifying how these types of responses are surfaced through the Google CloudWe are therefore happy to announce a change to the above-mentioned metrics for the following APIs: Directions API, Geocoding API, Maps Elevation API, Maps Static API, Places API, Street View Static API and Time Zone API.
Over the coming weeks, you will start seeing any , , Response status and Response code labels mapping in our Google Maps Platform Monitoring article.
DATA_NOT_AVAILABLE
,NOT_FOUND
orZERO_RESULTS
responses you receive on these APIs be reported in the Google Cloud monitoring metrics asgrpc_status_code: 5 (NOT_FOUND)
response_code: 404
,response_code_class: 4xx
instead of the unactionable old codes0 (OK)
200
,2xx
. For a full list of status code mappings across our different APIs, please see sectionCurrent rollout status:
You can further track the progress of the rollout by starring this public issue.
What do I need to do?
You don't need to do anything, but you can set up monitoring and alerting based on these codes.
You can go to the Metrics Explorer and Alerting sections under Monitoring, in the Google Cloud Console to experiment with the metrics. A simple example can be found here .
Tips
5
(NOT_FOUND)
,404
results for your application.5
(NOT_FOUND)
,404
responses changes over time.Examples
To get you started, here are a couple sample MQL queries to set up your monitoring graphs and alerts.
Example MQL graph for displaying breaking down your Google Map Platform request count by HTTP response code:
Relevant documentation:
https://cloud.google.com/monitoring/mql/examples#qlx-groupby-aggr
Example MQL graph for calculating the
404
ratio:Relevant documentation:
https://cloud.google.com/monitoring/mql/examples#qlx-filter-ratio
Example MQL alert triggered when the ratio of 404 errors is over the baseline of 60% over a 30-minute sliding window:
Relevant documentation:
https://cloud.google.com/monitoring/mql/reference#condition-tabop
Example MQL alert triggered when the ratio of 404s computed over a 30-minute sliding window increases by 20% compared to one hour earlier
Relevant documentation:
https://cloud.google.com/monitoring/mql/examples#qlx-ratios-over-time
https://cloud.google.com/monitoring/mql/examples#qlx-group-ratio
Further resources
For more information about how to use Google Cloud Monitoring with your Maps Platform usage, we recommend reading the following pages from our public documentation:
https://developers.google.com/maps/reporting-and-monitoring/overview
https://developers.google.com/maps/reporting-and-monitoring/monitoring
https://cloud.google.com/monitoring/api/metrics_gcp#gcp-maps
https://cloud.google.com/monitoring/mql
https://cloud.google.com/monitoring/mql/examples
https://cloud.google.com/monitoring/mql/reference
We’re here to help
If you have any questions please contact Google Maps Platform Support .
Thanks for choosing Google Maps Platform!
– The Google Maps Platform Team