|
1 | 1 | # Changelog
|
2 | 2 |
|
3 |
| -## Unreleased |
| 3 | +All notable changes to this project will be documented in this file. |
4 | 4 |
|
5 |
| -### API |
| 5 | +The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), |
| 6 | +and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). |
| 7 | + |
| 8 | +## [API 1.0.0-rc.3] - 2021-10-12 |
| 9 | + |
| 10 | +### Removed |
| 11 | + |
| 12 | +- Removed `opentelemetry:register_application_tracer`. Each application has a |
| 13 | + Tracer registered for it automatically on boot. This can be disabled by |
| 14 | + setting `opentelemetry` environment variable `register_loaded_applications` to |
| 15 | + `false`. |
| 16 | +- Named Tracers registered with `opentelemetry:register_tracer` are now stored |
| 17 | + separately from the mapping of Named Tracers created for each |
| 18 | + application. Meaning if you have a module `mod_a` in application `app_a` with |
| 19 | + application vsn `0.1.0` and also manually register a Tracer named `mod_a` with |
| 20 | + version `1.1.1` then use of macros like `?with_span` will use the `app_a` |
| 21 | + version `0.1.0` Named Tracer and manual use of a Named Tracer like: |
| 22 | + |
| 23 | + ``` |
| 24 | + Tracer = opentelemetry:get_tracer(mod_a), |
| 25 | + otel_tracer:with_span(Tracer, span_name, #{}, fun() -> ... end), |
| 26 | + ``` |
| 27 | + |
| 28 | + will use Named Tracer `mod_a` with version `1.1.1`. In previous versions after |
| 29 | + registering a Tracer named `mod_a` it would override the `mod_a` pointing to |
| 30 | + the `app_a` Tracer. |
| 31 | + |
| 32 | + Additionally, manual registration of a Named Tracer with the name `app_a` will |
| 33 | + not override the application registered Tracer of `app_a`. |
6 | 34 |
|
7 | 35 | #### Context
|
8 | 36 |
|
| 37 | +##### Added |
| 38 | + |
| 39 | +- B3 single header format support added |
| 40 | + |
| 41 | +##### Changed |
| 42 | + |
9 | 43 | - Propagators must now be implementations of a propagator type's behaviour. At
|
10 | 44 | this time only the `otel_propagator_text_map` behaviour exists. Callbacks for
|
11 | 45 | inject and extract take an optional "set" and "get" function for working with
|
|
26 | 60 | {text_map_injectors, [trace_context, baggage]},
|
27 | 61 | {text_map_extractors, [b3multi, trace_context, baggage]}
|
28 | 62 | ```
|
| 63 | + |
| 64 | +##### Fixed |
| 65 | +
|
29 | 66 | - `b3` propagator renamed `b3multi` to properly convey it is the version of the
|
30 | 67 | B3 spec that creates multiple headers
|
| 68 | +
|
| 69 | +## [SDK - 1.0.0-rc.3] - 2021-10-12 |
| 70 | +
|
| 71 | +### Fixed |
| 72 | +
|
| 73 | +- Memory leak fix: Non-recording Spans are no longer inserted into the ETS table tracking active span. |
| 74 | +- Ratio based root span sampling fixed, before it didn't take into account the |
| 75 | + generated trace id. |
0 commit comments