Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Record events for AppRTC and other demos #265

Closed
samdutton opened this issue Dec 4, 2014 · 3 comments
Closed

Record events for AppRTC and other demos #265

samdutton opened this issue Dec 4, 2014 · 3 comments

Comments

@samdutton
Copy link
Contributor

For example, to record numbers for those who, having navigated to apprtc.appspot.com:
• call gUM
• request a connection
• get a connection
• get errors
...

Could also add events for icon/button clicks on AppRTC and other demos.

@juberti juberti added the apprtc label Dec 4, 2014
@fippo
Copy link
Collaborator

fippo commented Dec 5, 2014

FWIW, here is the list of events we use for talky with a short description.

  • videoConnected (calls)
    in remotestreamadded; type (video/screen)
  • videoDisconnected
    in remotestreamremoved I think. Called only about 50% of the time since browser is closed
  • iceConnected (calls, really connected)
    candidatePair, whether ipv6 is used, whether a local/remote IPv6 candidate is available, setup time (measured from checking->connected)
  • iceFailed
    cause (called with a 30s timeout sometimes), local/remote turn/ipv6 candidate availability
  • localMedia (GUM success)
  • localMediaError (GUM failure)
    name (error code)
  • shareScreen
  • mute / unmute
    with media type (audio/video)

@samdutton
Copy link
Contributor Author

Thanks Philipp – that's really useful.

On Fri, Dec 5, 2014 at 6:28 PM, Philipp Hancke notifications@github.com
wrote:

FWIW, here is the list of events we use for talky with a short description.

  • videoConnected (calls) in remotestreamadded; type (video/screen)
  • videoDisconnected in remotestreamremoved I think. Called only about
    50% of the time since browser is closed
  • iceConnected (calls, really connected) candidatePair, whether ipv6
    is used, whether a local/remote IPv6 candidate is available, setup time
    (measured from checking->connected)
  • iceFailed cause (called with a 30s timeout sometimes), local/remote
    turn/ipv6 candidate availability
  • localMedia (GUM success)
  • localMediaError (GUM failure) name (error code)
  • shareScreen
  • mute / unmute with media type (audio/video)


Reply to this email directly or view it on GitHub
#265 (comment).

@vr000m
Copy link

vr000m commented Jan 9, 2015

In addition to those listed above we have:

  • iceDisconnected: if the interface disappears. If iceConnected again on the same or a different candidate pair, then we can pair disconnections and connections to calculate connectivity disruptions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants