Timeseries data structure

[steevej (Steeve Juneau)]

@georgelza

Would everyone agree that this is correct

That is in line with the documentation.

@georgelza

Would everyone agree that this is correct

I do

@georgelza

For me a a record/payload that have multiple key’s with measurement/values is not a time series specific record, it falls under data that sits better in a normal collection

No one is enforcing the use of this collection type. You may use normal collection if they fit better your use-case. Time series offer some benefits that may or may not be useful for your use-case. Storing measurements in buckets is one such benefits for space efficiency in particular.

@georgelza

guess this is also a valid structure.

{
  timestamp: 2024-10-01T02:00:00.000Z,
  metadata: {
    deviceId: 1002,
    sensorId: 90005,
    siteId: 1001,
    unit: 'celcius'
  },
  symbol: 'BTC-USD',
  price: 34104.1145,
  measurement: 12
}

Yes it is valid but not logical as you have a single unit in metadata but multiple values as your measurements. Personally, I would not put unit in the metadata but I would do put symbol in the metadata. I see the price as a series of time events related to a specific stock price.

My experience is quite limited with TS so I may be completely wrong. But it is an interesting discussion that I wanted to participate.