[jira] [Commented] (SENSSOFT-231) Add Micro Second Field in UserALE.js to cover Elastic indexing and time encoding issues.

["Rob Foley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SENSSOFT-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218438#comment-16218438 ] 

Rob Foley commented on SENSSOFT-231:
------------------------------------

Using the event timestamp and Date.now as a fallback, I've added a function that takes a timestamp (with decimal microseconds) and returns an object with separate millisecond and microsecond fields. Each of these fields is then added to the log.

The extension, as well as a couple of other places, uses performance.now, but generally it is up to the browser's default precision. This should mean backwards compatibility is unaffected. I've also added some quick tests to verify the timestamp handling works.

Currently the microseconds are tracked only up to 3 decimal places, as the precision suffers beyond that.

> Add Micro Second Field in UserALE.js to cover Elastic indexing and time encoding issues.
> ----------------------------------------------------------------------------------------
>
>                 Key: SENSSOFT-231
>                 URL: https://issues.apache.org/jira/browse/SENSSOFT-231
>             Project: SensSoft
>          Issue Type: Sub-task
>          Components: UserALE.js
>    Affects Versions: UserALE.js 0.2.0
>         Environment: JavaScript
>            Reporter: Joshua Poore
>            Assignee: Rob Foley
>            Priority: Critical
>             Fix For: UserALE.js 0.2.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Elastic is bad at micro second timing precision. 
> We need micro second timing to ensure that userale logs are being searched in their right order.
> We need to parse micro seconds and store them into a separate field.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)