Lenin Jaganathan

@shakuzen If the default behavior is made to publish relative to the start time, a few tests will fail because of the way they were written. I will try to...

@shakuzen Addressed the test failures in SignalFx library.

Added an additional commit to make the metrics timestamp synchronized across instances(report timestamp as the start of the current step) for SignalFx Meter Registry.

@shakuzen This issue seems to be there for around 2 years. And it's really hurting the short-lived batches where the data is never reported more than the long-lived applications. I...

@brharrington I agree that this will have some difficulty since the steps are completely randomized(but I believe this will be very negligible). The first option I tried was to just...

Agreed. I could see where the problem comes from. " the time taken to read them varies significantly" - For more clarity, let me try to use more accurate words....

Well, this issue is subtly different from the existing "commonTags" method which adds the commonTags to all the meters which are processed once every step interval.

Because it is not so efficient to do it every time we interact with the meter. A 1x1 example is OpenTelemetry's Resource, where unique information can be store once and...

@marcingrzejszczak How can we prevent an auto close on this issue?

@jonatan-ivanov / @shakuzen Is this something that can be looked for next milestone release?