Dear community,
We regret to inform you that we’ve made the difficult decision to discontinue Promscale, our unified metric and trace observability backend for Prometheus, Jaeger, and OpenTelemetry built on PostgreSQL and TimescaleDB.
You have a list of all the Promscale GitHub repositories below (we stopped maintaining or evolving them on April 30, 2023), as well as alternatives and frequently asked questions.
You will find several resources in our blog:
Timescale is a mature cloud database built on PostgreSQL. It supercharges PostgreSQL, giving it the boost it needs to handle large volumes of metrics, keeping your writes and queries fast via automatic partitioning, query planner enhancements, improved materialized views, columnar compression, and much more.
Check the Timescale Docs to learn more.
Keep reading.
Promscale was created to help the community use PostgreSQL/TimescaleDB as a fully compliant remote storage for Prometheus. Later on, we added OpenTelemetry and Jaeger tracing support.
With its full SQL support, it provided unified storage for traces and metrics with deep analysis and correlation capabilities. We also built tobs to simplify the deployment of a complete observability stack with one command.
Promscale has been a labor of love for our team at Timescale for over two years, and we’re grateful for the support and feedback from you, our community of users. However, after reevaluating our company priorities, we’ve decided to redirect our resources to other product areas.
We understand this news may be disappointing, so please see the FAQ for answers to common questions, including alternative solutions.
Thanks again for your support.
We’re refocusing all our efforts on the core of what we do best, creating a great developer experience for time-series application developers.
The following GitHub repositories and documentation will remain publicly available but will no longer be evolved nor maintained:
You can continue to use Promscale with TimescaleDB, although we don’t recommend it since Promscale will no longer be supported or maintained.
The GitHub repositories and release artifacts will remain publicly available.
We can’t ensure that Promscale will continue to work with newer versions of TimescaleDB and PostgreSQL. If you want to make modifications, we encourage you to fork the repositories.
Contact the support team at support@timescale.com or https://www.timescale.com/support.
There are different options depending on your use case. If you use Promscale as remote storage for Prometheus, there are a number of other options you can consider. There is a list provided in the Prometheus documentation.
If you are using Promscale as a storage system for your OpenTelemetry or Jaeger traces, there are a number of options you can consider.
This is a list of products that have native support for OpenTelemetry. You can use the OpenTelemetry Collector to convert your OpenTelemetry traces to Jager traces.
If you have a specific need, you can ask in the #promscale channel in Timescale's Community Slack, and we’ll try to help you.
About the author
By Ramon Guiu
TimescaleDB 2.22 & 2.23 – 90x Faster DISTINCT Queries, Postgres 18 Support, Configurable Columnstore Indexes, and UUIDv7 for Event-Driven Analytics
TimescaleDB 2.22 & 2.23: 90× faster DISTINCT queries, zero-config hypertables, UUIDv7 partitioning, Postgres 18 support, and configurable columnstore indexes.
Read more
Receive the latest technical articles and release notes in your inbox.
