[DEPRECATED] Promscale is a unified metric and trace observability backend for Prometheus, Jaeger and OpenTelemetry built on PostgreSQL and TimescaleDB.
PostgreSQL: 12.x, 13.x, 14.x, 15.x
TimescaleDB: >= 2.7.0 single-node (multi-node is not supported in this release)
Promscale Database Extension: >=0.8.0
| Connector | Extension | TSDB (single-node) | Postgres |
|---|---|---|---|
| 0.17.x | 0.8.x | 2.9.1 and above | 12.x, 13.x, 14.x, 15.x |
| 0.16.x | 0.7.x | 2.7.0 and above | 12.x, 13.x, 14.x |
| 0.15.x | 0.7.x | 2.7.0 and above | 12.x, 13.x, 14.x |
0.8 of the Promscale extension. You will also need TimescaleDB extension version 2.7.0 or above available. Then stop all Promscale Connector instances, upgrade the first one and restart it. The migration will happen automatically. Once the migration is completed, upgrade the remaining Promscale instances and restart them if needed.startup.dataset option in the config file for the dataset
configuration. Supersedes startup.dataset.config which accepts a string
instead of a mapping [#1737]We'd like to thank the following users for their contribution to this release:
startup.dataset.config
total suffix for gauge metrics and apply rate for countersevalInterval, but this setting can by used to make heavier queries run less often.Cache hit ratio panels.Promscale as a Jaeger-certified backend, performance improvements, and other bug fixes.
PostgreSQL: 12.x, 13.x, 14.x
TimescaleDB: >= 2.7.0 single-node (multi-node is not supported in this release)
Promscale Database Extension: >=0.7.0
0.7.0 of the Promscale extension. You will also need TimescaleDB extension version 2.7.0 or above available. Then stop all Promscale Connector instances, upgrade the first one and restart it. The migration will happen automatically. Once the migration is completed, upgrade the remaining Promscale instances and restart them if needed.FindTraces/Trace_spans_over_multiple_indices
Bug fixes and performance improvements in tracing(Jaeger & OTLP) subsystem.
PostgreSQL: 12.x, 13.x, 14.x
TimescaleDB: >= 2.7.0 single-node (multi-node is not supported in this release)
Promscale Database Extension: >=0.7.0
0.7.0 of the Promscale extension. You will also need TimescaleDB extension version 2.7.0 or above available. Then stop all Promscale Connector instances, upgrade the first one and restart it. The migration will happen automatically. Once the migration is completed, upgrade the remaining Promscale instances and restart them if needed.web.auth.ignore-path to skip http paths from authentication [#1637]tracing.streaming-span-writer to enable/disable streaming span writer. It is enabled by default. [#1633].tracing.async-acks by default [#1633].chunks_created metrics was removed. [#1634]timescaledb.telemetry_level=off [#1612]config_maintenance_jobs examplesIs
off
0 samples/sec in throughput by logging metric metadata throughput.use-timescaledb option from testswithTimescaleDB option from dataset configurationhttp://promscale:9202
PostgreSQL: 12.x, 13.x, 14.x
TimescaleDB: >= 2.7.0 single-node (multi-node is not supported in this release)
Promscale Database Extension: >=0.6
0.6 of the Promscale extension. You will also need TimescaleDB extension version 2.7.0 or above available. Then stop all Promscale Connector instances, upgrade the first one and restart it. The migration will happen automatically. Once the migration is completed, upgrade the remaining Promscale instances and restart them if needed.values.yaml file [#1551]-tracing.otlp.server-address in favour of -tracing.grpc.server-address [#1588]column "exemplar_label_values" does not exist (SQLSTATE 42703) on ingesting exemplars [#1574]/api/v1/labels & /api/v1/label/{name}/values to respond with labels of authorized tenants only [#1577]querier.LabelNames() in multi-tenancy._ps_trace.text_matches function introduced in extension version 0.6.0/api/v1/label/{name}/values API to respond with authorized tenants only./api/v1/labels: respond with labels of authorized tenants only when in multi-tenancy mode.tracing.grpc.server-address
action:benchmarks label is applied.logQueryStats
12.x, 13.x, 14.x.>= 2.6.1 single-node (multi-node is not supported in this release)0.5.4.0.5.4 of the Promscale extension. You will also need TimescaleDB extension version 2.6.1 or above available. Then stop all Promscale Connector instances, upgrade the first one and restart it. The migration will happen automatically. Once the migration is completed, upgrade the remaining Promscale instances and restart them if needed.PromscaleCacheTooSmall alert [#1498]db.num-writer-connections now sets the absolute number of write connections for writing metrics. [#1430]We'd like to thank @raphaelzoellner for his pull request[#1473].
db.num-writer-connections to set absolute number of writing connectionsTestSQLDropMetricChunk.-db.read-only mode.TestCompareTraceQueryResponse
prom_schema_migrations tablePromscaleCacheTooSmall alertThis release is a patch release to fix querying issues.
12.x, 13.x, 14.x.>= 2.6.1 single-node (multi-node is not supported in this release)>=0.5.x.0.5.x of the Promscale extension. You will also need TimescaleDB extension version 2.6.1 or above available. Then stop all Promscale Connector instances, upgrade the first one and restart it. The migration will happen automatically. Once the migration is completed, upgrade the remaining Promscale instances and restart them if needed.promql-per-step-stats feature.grafana/regexp to align with Prometheus.This release is a major step forward in our evolution of Promscale. It makes distributed tracing generally available and moves a lot of our logic into the Promscale database extension, allowing for further data optimization. Upgrades from previous versions of the system come with more caveats, please see below before upgrading.
Please note this release should only be used with the single-node version of TimescaleDB.
max_locks_per_transaction parameter on your database before starting the upgrade./healthz endpoint supports is GET. Some load balancers (e.g. HAProxy) that relied on the old behaviour need to be re-configured to use the verb GET instead.12.x, 13.x, 14.x
>= 2.6.1 single-node (multi-node is not supported in this release)>=0.5.0
pg_advisory_lock has been removed.promscale_sql namespace.--enable-feature=tracing and tracing.otlp.server-address=:9202 as the OTLP gRPC server by default listens to port 9202.promscale_ingest_channel_len_bucket metric and make it a gauge [#1177]promscale_ingest_max_sent_timestamp_milliseconds metric for tracing [#1270]promscale.conf
prom-migrator cannot migrate to HA setups.reset_metric_retention_period with two-step agg/api/v1/rules APIpromscale_ingest_max_sent_timestamp value for traces.add_prom_node
/api/v1/alerts API.promscale_ingest_channel_len metric and make it a Gauge.Starting with the 0.11.0 release, we will:
TimescaleDB 1.x
promscale_cache_ metric prefix [#1113]end < start. Start and end are swapped in this case [#1096]promscale_packager telemetry field for docker envs.