-
Notifications
You must be signed in to change notification settings - Fork 525
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
Force a timestamp on RUM data #723
Comments
@elastic/apm-server will this be included in 6.3 release? |
You tell me :), do you need it done for 6.3? |
Yes please :) , It would be great to get this into 6.3. |
jalvz
added a commit
to jalvz/apm-server
that referenced
this issue
Apr 3, 2018
jalvz
added a commit
to jalvz/apm-server
that referenced
this issue
Apr 9, 2018
jalvz
added a commit
to jalvz/apm-server
that referenced
this issue
Apr 11, 2018
jalvz
added a commit
that referenced
this issue
Apr 11, 2018
jalvz
added a commit
to jalvz/apm-server
that referenced
this issue
Apr 12, 2018
jalvz
added a commit
that referenced
this issue
Apr 12, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our experience has shown that we cannot rely on timestamps in data ( durations/elapsed time is fine) coming from browsers. It turns out that people routinely have computers that are completely our of sync with time or they have purposely backdated their clocks.
For this reason, we need the APM Server to set the current time on all the data that comes in through the client side endpoints.
Alternatively, we could make timestamp optional, make sure the JS agent doesn't set a timestamp, and let the APM Server set a timestamp on all the entries that don't have a timestamp set.
The text was updated successfully, but these errors were encountered: