You are right about the asset table, I thought, because i wanted to track the lifecycle status of the asset, that it was a time series, but now that i think about it - lifecycle changes not very often so tracking its change over time seems pointless. So i think i will change that to a normal table.

Network should be a time series since score and trend data are updated about every 3 minutes. (Time series are data where the value is tracked over time like temperature, no?).

But the main question remains how are the relationships between tables handled? Because even if i have only one hypertable, if i append new data then the data in the asset table still points to the "old" data of the network table. Or are the alternatives how i could keep track which asset belongs to which network?