senx / sensision Goto Github PK

How to reproduce:
curl http://127.0.0.1:9090/metrics

will always give timestamp in microseconds no matter what unit is set to.

Preliminary digging of the problem:

There is a typo in Sensition.SENSISION_TIME_UNIT

Even after fixing this, there seems to have hardcoded microseconds conversion (* 1000).
A class similar in spirit to warp10.continuum.TimeSource would be useful in sensision.

In Sensision.update method timestamp parameter should be in nanoseconds to avoid losing precision,
also need to convert to the unit used when forcing timestamp.

The method Sensition.update assumes the timestamp is in microseconds and push them to warp10 without conversion to the time unit in use.

To correctly convert to time unit without loosing precision update method should use nanoseconds instead of microseconds.

Note that it will break compatibility in warp10 that call Sensition.update with microseconds.