timescale/pg_prometheus repository overview

pg_prometheus is an extension for PostgreSQL that defines a Prometheus metric samples data type and provides several storage formats for storing Prometheus data.

This image is built with both pg_prometheus and TimescaleDB. It is built on top of the timescale/timescaledb image.

Please note: there is no latest tag for this image. See below for further explanation.

⁠Notable tags

• latest-pg11 - The latest release based on PostgreSQL 11
• latest-pg10 - The latest release based on PostgreSQL 10
• latest-pg9.6 - The latest release based on PostgreSQL 9.6
• Each release will also have those corresponding tags, e.g., 0.2.2-pg11, 0.2.2-pg10, and 0.2.2-pg9.6

⁠Notable links

• pg_prometheus and it's docker image repo - https://github.com/timescale/pg_prometheus⁠
• TimescaleDB itself - https://github.com/timescale/timescaledb⁠
• Our homepage - http://www.timescale.com/⁠

⁠Why is there no latest tag?

In general, it is usually a bad idea to track the latest tag for any Docker image, since you may get unexpectedly upgraded. For TimescaleDB (and pg_prometheus), this is particularly problematic because not only can the version of TimescaleDB change, but also the version of PostgreSQL. If we wanted our latest tag to always be the latest of all dependencies, users could be updated between major versions of PostgreSQL, which requires a pg_upgrade step. That may cause more hassles for the operator than expected. For a while (almost 2 years), we left latest pointing to our latest TimescaleDB version on PostgreSQL 9.6 -- this also is not a great experience since PG10 and PG11 offer a lot of improvements.

For these reasons, we do not offer a latest tag, but we do offer a 'latest' equivalent by publishing a latest tag for each PostgreSQL platform we support. For production systems, you should still be explicit about the version you want to use and not these latest tags, but at least you won't have to run a pg_upgrade step unexpectedly.