Re:Time-series data: Why (and how) to use a relational datab...
by cevian on Thursday April 20, 2017 @03:43PM
(#14160131)
Hey,
Not sure if this is part of the question but if you are querying the event data by something other than time (like a property of the event itself -- maybe the program return code in your example) than prometheus requires a full table scan since it does not have secondary indexes. With TimescaleDB you could add indexes on properties of the event data itself.
Re:Time-series data: Why (and how) to use a relational datab...
by dgacmu on Thursday April 20, 2017 @04:48PM
(#14160705)
Ahh, I think this answers my question. Painful - thank you!
Re:Time-series data: Why (and how) to use a relational datab...
by RobAtticus on Thursday April 20, 2017 @03:37PM
(#14160058)
I personally haven't used Prometheus much, so I'm not sure I can effectively answer (a). I don't see why this would be difficult in TimescaleDB though. If it's timestamped, it should work nicely with our hypertable abstraction and is as easy as a SQL INSERT.
Maybe others can chime in on the first part of your question though.
Re:Time-series data: Why (and how) to use a relational datab...
by dgacmu on Thursday April 20, 2017 @04:47PM
(#14160700)
So, if I have an event like "program observed a car at 2017-04-20 15:15:15.9939311", and I want to calculate summary statistics over time for that -- select count(*) where car_time % 86400 == foo". That's the one kind of query I've been finding problematic in Prometheus.
(Edited to add: This was answered by another reply -- Prometheus has to do a full table scan for things like this.)
(Yeah, I know, I'm asking the Internet to do my job for me... thank you, Internet!)