Open Bug 2074762 Opened 1 month ago Updated 1 month ago

Record telemetry for network geolocation responses that are not a usable location

Categories

(Toolkit :: Geolocation Provider, enhancement)

enhancement

Tracking

()

People

(Reporter: jstutte, Unassigned)

References

(Blocks 1 open bug)

Details

Bug 2073443 changes NetworkGeolocationProvider.fetchLocation so that a 2xx response is now a failure when its body is not JSON, or is JSON without a numeric location.lat / location.lng. These are counted under geolocation.network_failures, with the same labels as fetch() errors and non-2xx statuses. They no longer count as successes, but they also can't be told apart from other failures any more (raised by dparks in review of D327369).

We want to know how often this happens and where the bad responses come from. It could be the configured provider itself, or something between the client and the provider that answers 200 with its own page (captive portals, antivirus web shields, proxies).

Proposal:

  • A new labeled counter, e.g. geolocation.network_bad_responses, with labels non_json and no_location. Needs data review.
  • Possibly also record whether the response Content-Type was JSON. That would separate a change in the provider's response format from intercepted requests.

Related: after bug 2073443, clients with no geo.provider.network.url value no longer send requests at all. These are Windows 152+ clients that still have the network provider selected (bug 2037099, bug 2048776). They drop out of geolocation.geolocation_service and geolocation.network_failures entirely. If we still need to size that population, a counter for requests skipped because no service URL is configured could be added at the same time.

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.