1151647 - Improve candidate pair type telemetry

Status: NEW

(Core :: WebRTC: Signaling, defect, P3)

Description

[Byron Campen [:bwc]]

The existing candidate pair telemetry is probably our best metric for determining whether we've regressed our ICE success rate. But, it has some limitations:

1. It does not capture the "no candidates" case at all. This actually happens.
2. It does not capture cases where one stream (of multiple) is missing a full compliment of candidates (eg; stream 1 has relay candidates, but stream 2 does not). A similar problem exists for components within a stream.

It probably makes sense to do the following things:

1. Create new telemetry types WEBRTC_ICE_NO_LOCAL_CANDIDATES and WEBRTC_ICE_NO_REMOTE_CANDIDATES; we probably don't need the GIVEN_FAILURE/SUCCESS split since this simply can never work.

2. Modify how we calculate WEBRTC_CANDIDATE_TYPES_GIVEN_FAILURE/SUCCESS such that we only count a type as being present if it is in every component in every stream.

Comment 1

[Bulk Bug Changes for mreavy's org]

Mass change P2->P3 to align with new Mozilla triage process.