2 ms·
What I want in TimescaleDB is aggregation of old values in the SAME table. There is no use when I have to do this in a seperate table, Grafana overhead will be
by gsich 5y ago
What I want in TimescaleDB is aggregation of old values in the SAME table. There is no use when I have to do this in a seperate table, Grafana overhead will be insane.
- akulkarni 5y agoHave you looked at Real-time aggregates in TimescaleDB? It might help address the problem you are facing: "With real-time aggregation, when you query a continuous aggregate view, rather than just getting the pre-computed aggregate from the materialized table, the query will transparently combine this pre-computed aggregate with raw data from the hypertable that’s yet to be materialized. And, by combining raw and materialized data in this way, you get accurate and up-to-date results, while still enjoying the speedups that come from pre-computing a large portion of the result." https://blog.timescale.com/blog/achieving-the-best-of-both-worlds-ensuring-up-to-date-results-with-real-time-aggregation/ https://blog.timescale.com/blog/achieving-the-best-of-both-w... (You would then just need to query / point to the Continuous Aggregate to get the new and aggregated data in the same query)
- gsich 5y agoThanks!