Nice article but is it deliberate that you don't mention getting data into the database (line protocol or similar) or analysing the results and displaying them.
Input = use postGres
Output = Grafana has a postGres data source which I assume works and mention in timescales b's issues of a Grafana query helper.
Also lack of analysis, consolidation (continuous queries) and retention policies.
I am however intrigued as it does seem to hit my sweet spot of 100's of servers each with 5 to 10 different series of 10 metrics each, every 10 sec.
Database size might be an issue, as would the complexity of deployment (a big win for Prometheus rather than influxdb though).
Final thoughts
Can't help feeling this looks like a few input scripts running on postGres rather than a system solution for metrics and annotations.
Fellow Timescaler here. Thanks for the feedback. While we do not directly compare ingestion protocol and specific features, like continuous queries and retention polices (something I guess we could add), we do compare echosystems and third-party tools support, including ingestion (e.g., Kafka, Hibernate) and visualization (e.g., Tableau, Grafana). In fact, the developer behind the Grafana PostgreSQL data source is also a Timescaler, and an upcoming version of the data source will have an improved query builder and first-class TimescaleDB support.
Finally, I can assure you that this is more than a few input scripts. In fact, the project is thousands of lines of C code (if that matters) that implement automatic partitioning, query optimizations, and much more. Our code is open source here: https://github.com/timescale/timescaledb
Input = use postGres Output = Grafana has a postGres data source which I assume works and mention in timescales b's issues of a Grafana query helper.
Also lack of analysis, consolidation (continuous queries) and retention policies.
I am however intrigued as it does seem to hit my sweet spot of 100's of servers each with 5 to 10 different series of 10 metrics each, every 10 sec.
Database size might be an issue, as would the complexity of deployment (a big win for Prometheus rather than influxdb though).
Final thoughts Can't help feeling this looks like a few input scripts running on postGres rather than a system solution for metrics and annotations.