Skip to content

2.4.1 (Hotfix)

Choose a tag to compare

View all tags
@hazardfn hazardfn released this 07 Nov 13:21
· 89 commits to develop since this release
v2.4.1
e7eb25c

Bug Fixes

  • Time is now put into the event map lazily so you can specify it yourself if required. If you don't set this, be aware that any delays between when you send the event and when riemannx generates the timestamp can be reflected in your graphs hence why this is a bug - you should be allowed to specify your own timestamp instead of the client overwriting it.

Clarification

Imagine you send events to Riemannx with a timestamp and its inbox builds up because somewhere else all the scheduler time is being eaten up - when the scheduler is finally free Riemannx will process all the events as quickly as possible and Riemannx overwrites your timestamps - the timestamps of the events will be very close to each other and not reflect at ALL the time the event was actually sent (the time they sat in the inbox won't be taken into account).

There are other scenarios where the client completely overriding your specified time can cause issues (aside from it just being plain rude!) so you are advised to upgrade if you set the timestamp yourself.

Assets 2
Loading