Closed
Bug 1139317
Opened 10 years ago
Closed 9 years ago
Add "Failed calls count" to FHR for Firefox Hello
Categories
(Hello (Loop) :: Client, defect, P3)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: RT, Unassigned)
References
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
No description provided.
Reporter | ||
Updated•10 years ago
|
Priority: -- → P2
Comment 1•9 years ago
|
||
RT looking to see if this is metric we want
Flags: needinfo?(rtestard)
Priority: P2 → P3
Updated•9 years ago
|
Rank: 35
Comment 2•9 years ago
|
||
Adding to triage to see if we can resolve comment 1
Flags: needinfo?(rtestard)
Whiteboard: [triage]
Comment 3•9 years ago
|
||
We're no longer using FHR, so this bug doesn't apply
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Comment 4•9 years ago
|
||
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.
Description
•