Tracking.rb sends wrong creation timestamp to snowplow - it should send in milliseconds

Solution: Snowplow expects timestamps in milliseconds.

Background

dvce_created_tstamp in snowplow is wrong possibly due to a wrong timestamp being sent from Ruby. So we have 3 timestamps created sent and collector tstamp sent and collector are correctly set up not created

select derived_tstamp, dvce_sent_tstamp, dvce_created_tstamp, collector_tstamp, *
from snowplow.gitlab_events 
where 
  v_tracker LIKE 'rb-%'
limit 200
Edited by Alper Akgun