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

t_page value is not accurate in SPA page #149

Closed
weliame opened this Issue Aug 4, 2017 · 7 comments

Comments

Projects
None yet
3 participants
@weliame

weliame commented Aug 4, 2017

Hi team,
I tagged boomerang in my SPA project and it works.It's really a great tool! But there is something wrong with t_page time in my code. When I reload a page the value is accurate. When I click a link which will trigger route change, the t_page is not accurate. Following is from console output,

spa.missed:1
u:http://localhost:9010/components/spark-calendar/02_date_picker
v:0.9
vis.st:visible
ua.plt:MacIntel
ua.vnd:Google Inc.
nu:http://localhost:9010/components/spark-calendar/02_date_picker
rt.start:manual
rt.tstart:1501816088280
rt.bstart:1501816074769
rt.end:1501816088770
t_resp:90
**t_page:14197**
t_done:490
t_other:t_domloaded|-11508,boomerang|15006,boomr_fb|-13511
r:http://localhost:9010/components/spark-calendar/03_date_range
r2:
http.initiator:spa

You may see the t_page is really larger than t_done time.
Following is my code,

<script src="/images/boomr/boomerang.js"></script>
<script src="/images/boomr/spa.js"></script>
<script src="/images/boomr/auto-xhr.js"></script>
<script src="/images/boomr/history.js"></script>
<script src="/images/boomr/errors.js"></script>
<script src="/images/boomr/rt.js"></script>
<script>
    BOOMR.init({
        beacon_url: "http://localhost:8888/beacon",
        instrument_xhr: false,
        BW: {
            base_url: "https://github.com/SOASTA/boomerang/raw/master/images/",
            test_https: true,
            block_beacon: true
        }
    });
</script>
function hookHistoryBoomerang() {
  if (window.BOOMR && BOOMR.version) { // eslint-disable-line no-undef
    if (BOOMR.plugins && BOOMR.plugins.History) { // eslint-disable-line no-undef
      BOOMR.plugins.History.hook(history, true); // eslint-disable-line no-undef
    }
    return true;
  }
}

if (!hookHistoryBoomerang()) {
    if (document.addEventListener) {
        document.addEventListener('onBoomerangLoaded', hookHistoryBoomerang);
    } else if (document.attachEvent) {
        document.attachEvent('onpropertychange', (e) => {
            let evt = e || window.event;
            if (evt && evt.propertyName === 'onBoomerangLoaded') {
                hookHistoryBoomerang();
            }
        });
    }
}

Expect your idea and your info will help me a lot. Thanks in advance.

@weliame weliame changed the title from t_page data is not accurate in SPA page to t_page value is not accurate in SPA page Aug 4, 2017

@nicjansma

This comment has been minimized.

Show comment
Hide comment
@nicjansma

nicjansma Aug 4, 2017

Hi @weliame , it looks like t_page here is too high? 14197 vs 490 for t_done?

We have some bug fixes related to these calculations. Are you using the very latest code? If so, I'll see what other fixes we haven't backported to this branch yet.

nicjansma commented Aug 4, 2017

Hi @weliame , it looks like t_page here is too high? 14197 vs 490 for t_done?

We have some bug fixes related to these calculations. Are you using the very latest code? If so, I'll see what other fixes we haven't backported to this branch yet.

@weliame

This comment has been minimized.

Show comment
Hide comment
@weliame

weliame Aug 5, 2017

@nicjansma, thanks for your quick response. Yes, I mean t_page is too high. I suppose t_done = t_resp + t_page, right? I am using the latest code.

weliame commented Aug 5, 2017

@nicjansma, thanks for your quick response. Yes, I mean t_page is too high. I suppose t_done = t_resp + t_page, right? I am using the latest code.

@weliame

This comment has been minimized.

Show comment
Hide comment
@weliame

weliame Aug 8, 2017

Hi @nicjansma, is there any real example for React SPA monitor I can follow?

weliame commented Aug 8, 2017

Hi @nicjansma, is there any real example for React SPA monitor I can follow?

@nicjansma

This comment has been minimized.

Show comment
Hide comment
@nicjansma

nicjansma Aug 14, 2017

@weliame Like a sample app? I have a very simple one here:

http://dev.nicj.net/react/

And better general documentation here:

http://docs.soasta.com/boomerang/#react

nicjansma commented Aug 14, 2017

@weliame Like a sample app? I have a very simple one here:

http://dev.nicj.net/react/

And better general documentation here:

http://docs.soasta.com/boomerang/#react

@satya-ip

This comment has been minimized.

Show comment
Hide comment
@satya-ip

satya-ip Dec 15, 2017

Hi @nicjansma, is there any plan for VueJs SPA monitor? Pl share a link if there are any samples.

satya-ip commented Dec 15, 2017

Hi @nicjansma, is there any plan for VueJs SPA monitor? Pl share a link if there are any samples.

@nicjansma

This comment has been minimized.

Show comment
Hide comment
@nicjansma

nicjansma Dec 18, 2017

@satya-ip At this point we're encouraging everyone to use the History plugin with auto:true, which supports instrumentation of the window.history object and should track all user navigations that change the URL.

nicjansma commented Dec 18, 2017

@satya-ip At this point we're encouraging everyone to use the History plugin with auto:true, which supports instrumentation of the window.history object and should track all user navigations that change the URL.

@nicjansma

This comment has been minimized.

Show comment
Hide comment
@nicjansma

nicjansma Apr 20, 2018

@weliame We've posted our most recent updates that have several bug fixes for SPA calculations in #188. Please review and open a new Issue if you're still having problems!

nicjansma commented Apr 20, 2018

@weliame We've posted our most recent updates that have several bug fixes for SPA calculations in #188. Please review and open a new Issue if you're still having problems!

@nicjansma nicjansma closed this Apr 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment