You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One edge case that probably we should document is if one implementation decides to use CUMULATIVE and resets the start_time every export interval making this type essentially a DELTA. What should we recommend/do when in this case?
It's not clear why we should be concerned about this. This looks like a valid transformation, although it is sure to cause performance pains in some systems, for two reasons:
The client will have to remember the last value to correctly transform the cumulative into the delta representation.
A server that expects cumulative inputs will see each delta as a new timeseries, unless it has code to convert deltas back to cumulatives by comparing start_times and appending when possible.
Nevertheless, it's possible to reconstruct the correct state of the world from the data in this case. WAI?
One edge case that probably we should document is if one implementation decides to use
CUMULATIVE
and resets thestart_time
every export interval making this type essentially aDELTA
. What should we recommend/do when in this case?Originally posted by @bogdandrutu in #140
The text was updated successfully, but these errors were encountered: