Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

0.16.0
Compare
Choose a tag to compare
@github-actions github-actions released this 20 Oct 16:25
· 89 commits to master since this release
0.16.0
72c29aa

At a high level, this release contains

Promscale as a Jaeger-certified backend, performance improvements, and other bug fixes.

Requirements

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

Upgrade notes

  • Before starting the upgrade, please ensure that you have deployed version 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.

Improvements

  • Jaeger certification. Promscale is now a certified Jaeger backend and it passes all Jaeger storage backend tests. [#1621]
  • Improve the performance of trace id queries made from the Jaeger UI. [#1626]

Fixes

  • Fix queries returning no references/links when querying traces ingested using the native Jaeger API. [#1641]
  • Fix traces queries returning duplicated events and links (or logs and references in Jaeger) for traces with more than one event and one link. [#1678]
  • Fix incorrect reference types when retrieving Jaeger traces with multiple parent references. [#1681]
  • Fix incorrect population of span kind field in jaeger to get operations response.

Changelog

  • bdc733e .github: clean up code ownership
  • de48961 Add regex based skip list for jager integration tests
  • 045d01d Apply missing binary decode operation for batch.Process.Tags
  • 765ea4c Clone test spans before passing to SpanWriter
  • 8240a5b Fix FindTraces/Trace_spans_over_multiple_indices
  • 6e09316 Fix incorrect population of span kind field in jaeger getOperations response
  • f5fbaa1 Fix performance of trace id query
  • d0fc6f2 Fix retrieve traces query data inconsistencies
  • 10379d2 Instruction to use thanos-remote-read adapter for migrating data from Thanos.
  • a6d486c Optimize trace-id-time subquery
  • 72c29aa Prepare for 0.16.0 release
  • 7a2a4d1 Prepare for the 0.16.0 development cycle
  • 7831177 Preserve Jaeger RefType when storing/retrieving traces.
  • b98967c Refactor trace queries
  • e040f54 Refactor upgrade tests
  • 4dad1c0 Remove last bit of helm pieces
  • 7326873 Reuse CompareSliceOfTraces from jaeger_integration_tests package
  • ccde8ac Run Jaeger storage integration tests in separate GH actions job
  • d5a6eed Translate jaeger ref to otel span link with meta attributes
  • 79651c6 Use jaeger storage integration test fixtures from upstream
Assets 19
Loading