Skip to content

Commit

Permalink
Merge pull request #288 from tsloughter/bump-rc3
Browse files Browse the repository at this point in the history
bump version to 1.0.0-rc.3
  • Loading branch information
tsloughter authored Oct 12, 2021
2 parents 730124e + 18be678 commit 82337de
Show file tree
Hide file tree
Showing 2 changed files with 48 additions and 3 deletions.
49 changes: 47 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,45 @@
# Changelog

## Unreleased
All notable changes to this project will be documented in this file.

### API
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [API 1.0.0-rc.3] - 2021-10-12

### Removed

- Removed `opentelemetry:register_application_tracer`. Each application has a
Tracer registered for it automatically on boot. This can be disabled by
setting `opentelemetry` environment variable `register_loaded_applications` to
`false`.
- Named Tracers registered with `opentelemetry:register_tracer` are now stored
separately from the mapping of Named Tracers created for each
application. Meaning if you have a module `mod_a` in application `app_a` with
application vsn `0.1.0` and also manually register a Tracer named `mod_a` with
version `1.1.1` then use of macros like `?with_span` will use the `app_a`
version `0.1.0` Named Tracer and manual use of a Named Tracer like:

```
Tracer = opentelemetry:get_tracer(mod_a),
otel_tracer:with_span(Tracer, span_name, #{}, fun() -> ... end),
```

will use Named Tracer `mod_a` with version `1.1.1`. In previous versions after
registering a Tracer named `mod_a` it would override the `mod_a` pointing to
the `app_a` Tracer.

Additionally, manual registration of a Named Tracer with the name `app_a` will
not override the application registered Tracer of `app_a`.

#### Context

##### Added

- B3 single header format support added

##### Changed

- Propagators must now be implementations of a propagator type's behaviour. At
this time only the `otel_propagator_text_map` behaviour exists. Callbacks for
inject and extract take an optional "set" and "get" function for working with
Expand All @@ -26,5 +60,16 @@
{text_map_injectors, [trace_context, baggage]},
{text_map_extractors, [b3multi, trace_context, baggage]}
```
##### Fixed
- `b3` propagator renamed `b3multi` to properly convey it is the version of the
B3 spec that creates multiple headers
## [SDK - 1.0.0-rc.3] - 2021-10-12
### Fixed
- Memory leak fix: Non-recording Spans are no longer inserted into the ETS table tracking active span.
- Ratio based root span sampling fixed, before it didn't take into account the
generated trace id.
2 changes: 1 addition & 1 deletion apps/opentelemetry_api/VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.0.0-rc.2
1.0.0-rc.3

0 comments on commit 82337de

Please sign in to comment.