Skip to content

Force a timestamp on RUM data #723

Closed
@roncohen

Description

@roncohen

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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions