1984254 - Remove or update metrics expiring at the end of Firefox 144: networking.http_ip_addr_any_*

Status: RESOLVED FIXED

(Core :: Networking, task, P2)

Description

[telemetry-probes]

The following metrics will expire at the end of Firefox Nightly release: version 144.

networking.http_ip_addr_any_count
networking.http_ip_addr_any_hostnames

What to do about this:

1. If one, some, or all of the metrics are no longer needed, please remove them from their metrics.yaml definition file.
2. If one, some, or all of the metrics are still required, please submit a patch to extend their expiry.

If you have any problems, please ask for help on the #glean Matrix room or the #data-help Slack channel.
We'll give you a hand.

Your Friendly Neighbourhood Glean Team

---

This bug was auto-filed by probe-scraper.

Comment 1

[Valentin Gosu [:valentin]]

Capturing the results from glean:

http_ip_addr_any_hostnames - 2025-07-17 18:00:00 - 34,345 clients 7,647,892,390 samples
http_ip_addr_any_count - 2025-07-17 18:00:00 - 1,676,019 clients 7,159,096,110 samples

So it would seem that only 34K clients ever accessed 0.0.0.0 via the domain name - the rest of them ~1.6 million have ever tried to create a 0.0.0.0 or ::0 socket but that came from DNS.

I think the decision to disable access to 0.0.0.0 makes a lot of sense, and we can let it ride the trains.
I think we can probably remove these now?
CC Sunil

Comment 2

[Sunil Mayya]

Attachment: Bug 1984254 - Remove expiring telemetry probes and enable network.socket.ip_addr_any.disabled for all users. r=#necko

Remove http_ip_addr_any_count and http_ip_addr_any_hostnames telemetry probes
that were set to expire in Firefox 145. The telemetry collection code has been
removed from nsHttpChannel.cpp, HttpConnectionUDP.cpp, and nsSocketTransport2.cpp.

Enable the network.socket.ip_addr_any.disabled preference for all users by
changing the value from @IS_EARLY_BETA_OR_EARLIER@ to true. Based on telemetry
data showing minimal usage of 0.0.0.0 addresses, this security protection
should be enabled for the entire user base.

Co-Authored-By: Claude

Comment 3

[Sunil Mayya]

(In reply to Valentin Gosu [:valentin] (he/him) from comment #1)

Capturing the results from glean:

http_ip_addr_any_hostnames - 2025-07-17 18:00:00 - 34,345 clients 7,647,892,390 samples
http_ip_addr_any_count - 2025-07-17 18:00:00 - 1,676,019 clients 7,159,096,110 samples

So it would seem that only 34K clients ever accessed 0.0.0.0 via the domain name - the rest of them ~1.6 million have ever tried to create a 0.0.0.0 or ::0 socket but that came from DNS.

I think the decision to disable access to 0.0.0.0 makes a lot of sense, and we can let it ride the trains.
I think we can probably remove these now?
CC Sunil

Fixed by claude :) -> https://phabricator.services.mozilla.com/D262216

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/4b63e8e14125
https://hg.mozilla.org/integration/autoland/rev/01313dea0f28
Remove expiring telemetry probes and enable network.socket.ip_addr_any.disabled for all users. r=necko-reviewers,valentin

Comment 5

[Cristina Horotan [:chorotan]]

https://hg.mozilla.org/mozilla-central/rev/01313dea0f28