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
start_time_unixnano is likely going to be the same for all data point in timeseries. Moving this to timeseries message instead of putting it in the value (as it is now) will be a space and speed optimization.
The text was updated successfully, but these errors were encountered:
I've wondered about this too. If you were collecting metrics over a large interval, especially for measure metrics, you would probably want individual timestamps, which is what OpenMetrics has specified. However it's wasteful in an SDK where you expect to export frequently. I'd leave both as options. OpenMetrics allows the timestamp to be omitted, in which case the backend uses its own, but I would prefer it to be an explicit field associated with the whole report.
start_time_unixnano is likely going to be the same for all data point in timeseries. Moving this to timeseries message instead of putting it in the value (as it is now) will be a space and speed optimization.
The text was updated successfully, but these errors were encountered: