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

fix(performance): send post to kuma for custom ie-load-event-end metric #1001

Merged
merged 1 commit into from
Jun 28, 2018
Merged

fix(performance): send post to kuma for custom ie-load-event-end metric #1001

merged 1 commit into from
Jun 28, 2018

Conversation

schalkneethling
Copy link

@tkadlec This will post a message to Kuma to set a custom mark at the same time as we send performance.timing.loadEventEnd for GA beaconing.

On the Kuma side I will then also set a new custom mark in the head of the pages similar to https://github.com/mdn/interactive-examples/blob/master/js/editor-libs/perf.js#L18

I will then also set a new measure which will use the mark from the head in Kuma as startMark and then the mark we are creating here as endMark. That should then give us the duration equal to ie-load-complete

Let me know your thoughts. Thanks!

@schalkneethling schalkneethling added enhancement Improves an existing feature. performance labels Jun 27, 2018
@schalkneethling schalkneethling added this to the Sprint 1 Q3 2018 milestone Jun 27, 2018
@tkadlec
Copy link

tkadlec commented Jun 27, 2018

I will then also set a new measure which will use the mark from the head in Kuma as startMark and then the mark we are creating here as endMark. That should then give us the duration equal to ie-load-complete

I may not be following, but why do we need a custom mark in the head of Kuma for startMark? I think if we use navigationStart as our startMark and this mark as the endMark we should have an accurate picture of what's going on.

@schalkneethling
Copy link
Author

@tkadlec As I posted that, I was thinking exactly that :) Other than that, does this look good to you?

@tkadlec
Copy link

tkadlec commented Jun 27, 2018

Yeah, other than that I think we're in good shape!

@schalkneethling schalkneethling merged commit 77a093e into mdn:master Jun 28, 2018
wbamberg pushed a commit to wbamberg/interactive-examples that referenced this pull request Jul 12, 2018
* upstream/master: (33 commits)
  Add HTML example for <a> (issue mdn#1014) (mdn#1022)
  fix(tabbed): load fonts as part of the editor css as @font-face does not work inside shadow dom (mdn#1015)
  html/input: Lowercase attributes (mdn#1024)
  Add color-adjust property example (mdn#1008)
  chore(deps): update dependency eslint to v5.1.0 (mdn#1023)
  chore(community): add @goodwin64 as contributor (mdn#1021)
  chore(community): add @dagolinuxoid as contributor (mdn#1020)
  chore(community): add @arai-a as contributor (mdn#1019)
  chore(community): add @ro-ka as contributor (mdn#1018)
  Issue mdn#1013 <style> elements in HTML editor break editor's render method (mdn#1017)
  chore(deps): update jest monorepo to v23.3.0 (mdn#1012)
  Issue#946 open links in new tab (mdn#1009)
  Send metric only during loading event (mdn#1011)
  fix(performance): only send loading mark inside loading event (mdn#1010)
  chore(deps): update dependency prettier to v1.13.7 (mdn#1006)
  fix(address): add name to the provided address (mdn#1004)
  chore(community): add @Arkangus as contributor (mdn#1002)
  Correct "expected output" mistake (mdn#1000)
  fix(performance): send post to kuma for custom ie-load-event-end metric (mdn#1001)
  chore(deps): update jest monorepo to v23.2.0 (mdn#993)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improves an existing feature.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants