Confirmed users
632
edits
Loop/Data Collection: Difference between revisions
Jump to navigation
Jump to search
→Call Setup Latency
| Line 82: | Line 82: | ||
* For initial analysis, we could probably do with something as simple as a report that says "on ''date'', there were ''x'' failures, broken down as follows: failed: ''failed count'', disconnected: ''disconnected count''," and then lets us list all the failures for a given date/reason pair, ultimately allowing us to download the log to analyze. As we get experience with how things tend to break, we might want to refine this some, but it's a good start. | * For initial analysis, we could probably do with something as simple as a report that says "on ''date'', there were ''x'' failures, broken down as follows: failed: ''failed count'', disconnected: ''disconnected count''," and then lets us list all the failures for a given date/reason pair, ultimately allowing us to download the log to analyze. As we get experience with how things tend to break, we might want to refine this some, but it's a good start. | ||
== Call | == Call Quality Metrics == | ||
This covers collection of the following information: | |||
* Call setup latency | |||
* Media metrics (RTT, jitter, loss) | |||
Tracked in {{bug|1003163}} | Tracked in {{bug|1003163}} | ||