-
Notifications
You must be signed in to change notification settings - Fork 33
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
Handle new data format #49
Comments
Related (I think, not checked properly): akamai/boomerang#68 |
Hi, I was just wondering if there is any news on this? I've just run into this (getting a 400 "Invalid data" error) after trying to use the latest version of Boomerang with restiming. |
@JonHouse, I realise this is a sub-optimal answer, but are you able to work round this by using an older version of boomerang at all? Speaking personally, it is not something I expect to have time to work on in the near future. Failing that, maybe there is somebody at Springer Nature who can look into this, @dotcode? |
Hi @philbooth, thanks for getting back to me so quickly. I have reverted to the version of restiming.js before this change was merged and that seems to work so I'll stick with that, thanks again. |
The compression/decompression is implemented here: https://github.com/nicjansma/resourcetiming-compression.js feel free to pull the code into boomcatch. |
@dotcode, have you got any Nature peeps available who might be available to take a stab at this? If not I'll make time for it at some point but probably not for a few weeks. |
where can i find older version of retiming.js which can be used with boom catch?? |
you'll have to use `git log` and `git checkout` to go back in history.
however note that older versions also have bugs that mean the data is not
reliable.
|
@bluesmoon Do you foresee elasticsearch as a possible & correct endpoint for boomerang (nt, rt, restiming, etc...) data.... Or do you see any issues with that approach.... We wrote a Java interceptor for flume that converted all the data from NT, RT and Restiming to elasticsearch.. but somehow we are yet to make sense of that data... maybe structurally etc. |
@softwareklinic I think that's off topic for this thread. |
has this been implemented --- |
Hi @softwareklinic, unfortunately we don't have anyone at the moment working in this project so I don't expect this to be fixed any time soon. |
Has anyone got the new decompression to work? I'm looking into now but wanted to post in case someone else has beat me to it. |
@josebolos Do you have any work towards an update for 4.0? |
Created a pull request to fix this: #95 |
As per: http://nicj.net/compressing-resourcetiming/
The text was updated successfully, but these errors were encountered: