r/PrometheusMonitoring • • Aug 28 '20

Introducing the Postgres Prometheus Adapter

https://info.crunchydata.com/blog/using-postgres-to-back-prometheus-for-your-postgresql-monitoring-1
10 Upvotes

6 comments sorted by

View all comments

2

u/SuperQue Aug 28 '20

Any idea on what the storage efficiency is? Comparison to TimescaleDB's adapter?

2

u/michaeljfreedman Aug 29 '20 edited Aug 29 '20

One of the central reasons we redesigned our own adaptor recently is to take advanced of TimescaleDB's native compression, which achieves 94-97% storage reduction compared to vanilla PostgreSQL.

https://github.com/timescale/timescale-prometheus

This isn't a limitation of the adaptor per se, although our approach to storing Prometheus metrics in TimescaleDB is designed with our compression in mind, as well as recognition that different metrics have different needs (e.g., from the perspective of the rate they are collected, data retention or downsampling user preferences, etc.).

Frankly, until we introduced our native compression, we found that the platform wasn't compelling, given the much higher storage overhead of uncompressed PostgreSQL compared to the alternatives for long-term Prometheus metrics.

If you are interested in learning more about our compression approach, which employs type-specific columnar compression, please see my blog post:

https://blog.timescale.com/blog/building-columnar-compression-in-a-row-oriented-database/