Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Philip Tellis
    @bluesmoon
    yeah
    Quinten Pohl
    @quintenp
    Bad practise since you could easily log pci data which can net you serious issues since the GDPR laws
    Mitch McKenzie
    @mitchmckenzie
    @bluesmoon : For a given request that the auto-xhr plugin handles ... I want the beacon data to include the body of the request (aka the request payload) , in my case it will be a blob of JSON data
    Quinten Pohl
    @quintenp
    @bluesmoon ever thought about using fetch api
    Mitch McKenzie
    @mitchmckenzie
    I want the data so I can scrap it out later for reporting purposes
    Quinten Pohl
    @quintenp
    So fetch ->sendBeacon->she
    Xhr
    Mitch McKenzie
    @mitchmckenzie
    not sure I follow
    Quinten Pohl
    @quintenp
    Not relevant to your ask @mitchmckenzie
    Mitch McKenzie
    @mitchmckenzie
    ok
    thought you were talking about my question
    Quinten Pohl
    @quintenp
    @mitchmckenzie you can easily do it write your own code that grabs the body in the autoxhr plugin or event
    Mitch McKenzie
    @mitchmckenzie
    i wonder if I can snag it in the before beacon event
    Quinten Pohl
    @quintenp
    I was asking @bluesmoon if he considered using fetch api->sendBeacon->xhr when sending beacons in that order
    Better support across the board
    Also @bluesmoon I considered adding timing to the unload event since people can execute some real nasty code there. E.g. if you fire xhr while unloading you can block a navigation or close. The only problem would be sending the data onwards should they nav out the boomr zone
    Quinten Pohl
    @quintenp
    @mitchmckenzie you could there are other means as well, eg. what happens with your response? Is there a downstream process that can add it via BOOMR.AddVar()
    but easy enough in either case
    Mitch McKenzie
    @mitchmckenzie
    looks like the xhr_send and xhr_load will give me the ability to grab data elements from request/response payloads
    Mitch McKenzie
    @mitchmckenzie
    I have a pdf that loads inside of an iframe... what's the best way to leverage boomerang to time loading the pdf?
    Philip Tellis
    @bluesmoon
    You'd have to attach to the iframe's onload event. Resource Timing may have info, but the iframe itself doesn't have a window object.
    Samar Panda
    @samarpanda
    Is npm run test expected to run locally? Wondering why is it breaking at "karma:unit:ChromeHeadless"? Below is the message what i get
    Running "strip_code:debug" (strip_code) task
    
    Running "strip_code:prod" (strip_code) task
    
    Running "karma:unit:ChromeHeadless" (karma) task
    05 10 2018 11:16:34.172:WARN [watcher]: Pattern "/Users/apple/projects/boomerang/tests/vendor/mocha/mocha.css" does not match any file.
    05 10 2018 11:16:34.174:WARN [watcher]: Pattern "/Users/apple/projects/boomerang/tests/vendor/mocha/mocha.js" does not match any file.
    05 10 2018 11:16:34.175:WARN [watcher]: Pattern "/Users/apple/projects/boomerang/tests/vendor/assertive-chai/dist/assertive-chai.js" does not match any file.
    05 10 2018 11:16:34.210:INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:4000/
    05 10 2018 11:16:34.211:INFO [launcher]: Launching browser ChromeHeadless with unlimited concurrency
    05 10 2018 11:16:34.215:INFO [launcher]: Starting browser ChromeHeadless
    05 10 2018 11:16:34.716:INFO [HeadlessChrome 69.0.3497 (Mac OS X 10.14.0)]: Connected on socket vDRuKUkbdmMr8hn0AAAA with id 41279479
    HeadlessChrome 69.0.3497 (Mac OS X 10.14.0) ERROR
      Uncaught ReferenceError: chai is not defined
      at unit/00-logging.js:5
    
    HeadlessChrome 69.0.3497 (Mac OS X 10.14.0) ERROR
      Uncaught ReferenceError: chai is not defined
      at unit/00-logging.js:5
    
    1..0
    05 10 2018 11:16:34.833:INFO [karma-tap-reporter]: writing report to file: /Users/apple/projects/boomerang/tests/results/unit.tap
    Warning: Task "karma:unit:ChromeHeadless" failed. Use --force to continue.
    
    Aborted due to warnings.
    npm ERR! Test failed.  See above for more details.
    Is anyone else getting similar error? Please share some pointer to make this work.
    Samar Panda
    @samarpanda
    Got pointers from this akamai/boomerang#197 thread. Let me try if it address my problem.
    Samar Panda
    @samarpanda
    Below are the steps i took. My bad i missed running bower install earlier
    npm i bower
    node_modules/.bin/bower install
    Quinten Pohl
    @quintenp
    When boomerang continuity plugin has tti.m set to "raf"
    what is the value to look at then
    @bluesmoon
    Quinten Pohl
    @quintenp
    @nicjansma
    anyone :S
    if c.tti.m=raf what is the value to look at in this case
    Philip Tellis
    @bluesmoon
    I don't understand the question. What is the value to look at for what?
    You would always use c.tti regardless of the value of c.tti.m
    Quinten Pohl
    @quintenp
    Ah ok thanks thought it was to be used as a form of fallback
    Like c.tti is there but you can use c.tti.m matching field as a form of a alternative
    Graham Coombe
    @gcoombe
    Had a question here but realized gitter might be a better place for this: akamai/boomerang#262
    I'm having a little trouble getting the initial spa.hard event firing with a react app
    Graham Coombe
    @gcoombe
    It only fires if I have a redirect on my initial load. So if I reload the page on "/" and it auto redirects to "/overview" it works fine but not if I reload the page directly on "/overview". Looking through the code I can't figure out exactly what should be firing the event since there's no function being called on the history object.
    Graham Coombe
    @gcoombe
    It seems to work if I always set hadRouteChange to true but I would like to understand this better
    Philip Tellis
    @bluesmoon
    @gcoombe I think someone's going to respond on the bug
    Andreas Marschke
    @andreas-marschke
    @gcoombe Hey Graham! I think you don't need the history direct instrumentation at this point you should be able to just enable the History plugin before your Spa Hard nav happens and it should get the information for you. I replied in essence on the issue. Hope this helps.
    Graham Coombe
    @gcoombe
    Thanks for your help @andreas-marschke ! That's kind for what I figured from poking through the code :thumbsup:
    Graham Coombe
    @gcoombe

    Sorry one more question @andreas-marschke I have a react app which on load typically:
    1) Loads a bundle
    2) Shows a nav bar and loading spinner while it does an initial graphql call
    3) Once the graphql completes shows the main content

    Currently it seems like spa events wait for the graphql call to finish but not spa_hard events. Is it possible to get both to wait? Our page isn't really usable until the call finishes. Thanks!

    Graham Coombe
    @gcoombe
    I suspect it's because the xhr calls occurs before the onLoad event, as such the spa_hard event gets added to the auto-xhr mutation handler after the initial xhr calls. They then aren't marked as nodes that must complete for the spa_hard event to fire.
    Graham Coombe
    @gcoombe
    This is a quick and dirty version of what I'm looking for https://github.com/gcoombe/boomerang/tree/spa-hard-wait-for-xhr
    pratikgolchha
    @pratikgolchha
    I want to remove boomerang details from console. Can someone please help?
    Philip Tellis
    @bluesmoon
    @pratikgolchha I've responded on the github issue that you opened.
    Andreas Marschke
    @andreas-marschke
    @gcoombe You could just as well artificially hold the beacon until after the last events have come back with a custom Boomerang Plugin. This should not have an impact on your overall reported performance data mind you.
    Enes Genç
    @enesfurkangenc
    Hey, i have question. im using try boomerang. I use iframes in my application. I want to capture xhr requests in these iframes. But i cannot ..Can someone please help?