All Versions
20
Latest Version
Avg Release Cycle
66 days
Latest Release
1110 days ago

Changelog History
Page 2

  • v2.3.0 Changes

    September 15, 2018

    โž• Added

    • Spandex.current_context/1 and Spandex.Tracer.current_context/1 functions, which get a Spandex.SpanContext struct based on the current context.
    • Spandex.inject_context/3 and Spandex.Tracer.inject_context/2 functions, which inject a distributed tracing context into a list of HTTP headers.

    ๐Ÿ”„ Changed

    • The Spandex.Adapter behaviour now requires an inject_context/3 callback, which encodes a Spandex.SpanContext as HTTP headers for distributed tracing.
  • v2.2.0 Changes

    September 15, 2018

    โž• Added

    • The Spandex.Trace struct now includes priority and baggage fields, to support priority sampling of distributed traces and trace-level baggage, respectively. More details about these concepts can be found in the OpenTracing documentation. An updated version of the spandex_datadog library will enable support for this feature in terms of the Spandex.Adapter and Sender APIs.

    ๐Ÿ”„ Changed

    • It is no longer required that you specify the env option. If not specified, it will default to nil. This is useful, for example, for allowing the Datadog trace collector configured default to be used.
    • The Spandex.Adapter.distributed_context/2 callback now expects a SpanContext struct to be returned, rather than a Map.
    • Similarly, the Spandex.continue_trace function now expects a SpanContext struct rather than a separate trace_id and span_id.
    • The sender API now calls the send_trace function, passing in a Spandex.Trace struct, rather than passing a list of Spandex.Span structs. This means that you need to update the spandex_datadog to a compatible version.

    ๐Ÿ—„ Deprecated

    • ๐Ÿ—„ Spandex.continue_trace/4 is deprecated in favor of Spandex.continue_trace/3
    • ๐Ÿ—„ Similarly, Tracer.continue_trace/4 is deprecated in favor of Tracer.continue_trace/3
  • v2.1.0 Changes

    September 15, 2018

    โฌ†๏ธ It is recommended to reread the README, to see the upgrade guide and understand the changes.

    โž• Added

    • Massive changes, including separating adapters into their own repositories

    ๐Ÿ”„ Changed

    • Many interface changes, specifically around return values

    โœ‚ Removed

    • Adapters now exist in their own repositories
  • v2.0.0 Changes

    September 15, 2018

    โž• Added

    • Massive changes, including separating adapters into their own repositories

    ๐Ÿ”„ Changed

    • Many interface changes, specifically around return values

    โœ‚ Removed

    • Adapters now exist in their own repositories
  • v1.6.1 Changes

    June 04, 2018

    โž• Added

    • โšก๏ธ private key, when updating spans, for non-inheriting meta
  • v1.6.0 Changes

    June 04, 2018

    โž• Added

    • Storage strategy behaviour

    ๐Ÿ”„ Changed

    • Centralize most storage logic, requiring only the most adapter specific behaviour to be defined by the adapter.
  • v1.5.0 Changes

    June 02, 2018

    ๐Ÿ”„ Changed

    • ๐Ÿ“‡ Interface for updating span metadata, and creating with metadata has been updated
    • ๐Ÿ“š Check documentation for examples
  • v1.4.1 Changes

    May 31, 2018

    ๐Ÿ”„ Changed

    • ๐Ÿ“œ Resolved an issue with distributed trace header parsing
  • v1.4.0 Changes

    May 29, 2018

    โž• Added

    • The tracer pattern
    • ๐Ÿ”ง Modernized configuration
    • More: Please read the readme again!
  • v1.3.4 Changes

    May 25, 2018

    โž• Added

    • ๐Ÿ‘Œ Support distributed tracing via trace headers.
    • โž• Added a changelog

    ๐Ÿ”„ Changed

    • No new changes