Add "Failed calls count" to FHR for Firefox Hello

RESOLVED INVALID

Status

P3
normal
Rank:
35
RESOLVED INVALID
4 years ago
3 years ago

People

(Reporter: RT, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [triage])

User Story

Bug 1123660 addressed counting successful Hello sessions and categorizing them per session duration buckets.

This bug is about counting failed Hello sessions and adding this information to FHR.

Acceptance criteria:
-FHR includes the following Hello data
  * Number of failed Hello sessions
  * Number of successful Hello sessions per session duration category (short/medium/long) [already addressed in bug 1123660 ]

Hello successful session definition: direct call, URL call-back or conversation instance where 2 peers are concurrently present with bi-directionnal media for more than 10s. We are counting here every session regardless of whether the browser user is the A party or the B party.

Hello failed session definition: initiated direct call or conversation instance where both peers could not success in being present with bi-directionnal media or could but for less than 10s. We are counting here every session regardless of whether the browser user is the A party or the B party.

Short session definition: 10 seconds to 30s (inclusive)
Medium session definition: Between 31s and 5 minutes
Long session definition: Over 5 minutes
Comment hidden (empty)
(Reporter)

Updated

4 years ago
User Story: (updated)
Depends on: 1123660
(Reporter)

Updated

4 years ago
No longer depends on: 1123660
(Reporter)

Updated

4 years ago
Depends on: 1123660
(Reporter)

Updated

4 years ago
Priority: -- → P2

Comment 1

3 years ago
RT looking to see if this is metric we want
Flags: needinfo?(rtestard)
Priority: P2 → P3
Rank: 35
Adding to triage to see if we can resolve comment 1
Flags: needinfo?(rtestard)
Whiteboard: [triage]
We're no longer using FHR, so this bug doesn't apply
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
Also note we now get this information through loop-server
You need to log in before you can comment on or make changes to this bug.