|
2 | 2 |
|
3 | 3 | ## vNext |
4 | 4 |
|
| 5 | +## v0.24.1 |
| 6 | + |
| 7 | +- Add hidden method to support tracing-opentelemetry |
| 8 | + |
5 | 9 | ## v0.24.0 |
6 | 10 |
|
7 | 11 | - Add "metrics", "logs" to default features. With this, default feature list is |
|
34 | 38 | - Added `non_exhaustive` annotation to [`trace::Config`]. Marked [`config`] as deprecated since it's only a wrapper for `Config::default` |
35 | 39 | - Removed [`Tracer::tracer_provder`] and [`Tracer::instrument_libraries`] as it's not part of the spec. |
36 | 40 |
|
37 | | -- **Breaking** [#1830](https://github.com/open-telemetry/opentelemetry-rust/pull/1830/files) [Traces SDK] Improves |
| 41 | +- **Breaking** [#1830](https://github.com/open-telemetry/opentelemetry-rust/pull/1830/files) [Traces SDK] Improves |
38 | 42 | performance by sending Resource information to processors (and exporters) once, instead of sending with every log. If you are an author |
39 | 43 | of Processor, Exporter, the following are *BREAKING* changes. |
40 | 44 | - Implement `set_resource` method in your custom SpanProcessor, which invokes exporter's `set_resource`. |
41 | 45 | - Implement `set_resource` method in your custom SpanExporter. This method should save the resource object |
42 | 46 | in original or serialized format, to be merged with every span event during export. |
43 | | - - `SpanData` doesn't have the resource attributes. The `SpanExporter::export()` method needs to merge it |
| 47 | + - `SpanData` doesn't have the resource attributes. The `SpanExporter::export()` method needs to merge it |
44 | 48 | with the earlier preserved resource before export. |
45 | 49 |
|
46 | 50 | - **Breaking** [1836](https://github.com/open-telemetry/opentelemetry-rust/pull/1836) `SpanProcessor::shutdown` now takes an immutable reference to self. Any reference can call shutdown on the processor. After the first call to `shutdown` the processor will not process any new spans. |
@@ -95,17 +99,17 @@ The `LogRecord::target` field contains the actual target/component emitting the |
95 | 99 | - **Breaking** [#1624](https://github.com/open-telemetry/opentelemetry-rust/pull/1624) Remove `OsResourceDetector` and |
96 | 100 | `ProcessResourceDetector` resource detectors, use the |
97 | 101 | [`opentelemetry-resource-detector`](https://crates.io/crates/opentelemetry-resource-detectors) instead. |
98 | | -- [#1636](https://github.com/open-telemetry/opentelemetry-rust/pull/1636) [Logs SDK] Improves performance by sending |
| 102 | +- [#1636](https://github.com/open-telemetry/opentelemetry-rust/pull/1636) [Logs SDK] Improves performance by sending |
99 | 103 | Resource information to processors (and exporters) once, instead of sending with every log. If you are an author |
100 | 104 | of Processor, Exporter, the following are *BREAKING* changes. |
101 | 105 | - Implement `set_resource` method in your custom LogProcessor, which invokes exporter's `set_resource`. |
102 | 106 | - Implement `set_resource` method in your custom LogExporter. This method should save the resource object |
103 | 107 | in original or serialized format, to be merged with every log event during export. |
104 | | - - `LogData` doesn't have the resource attributes. The `LogExporter::export()` method needs to merge it |
| 108 | + - `LogData` doesn't have the resource attributes. The `LogExporter::export()` method needs to merge it |
105 | 109 | with the earlier preserved resource before export. |
106 | 110 | - Baggage propagation error will be reported to global error handler [#1640](https://github.com/open-telemetry/opentelemetry-rust/pull/1640) |
107 | 111 | - Improves `shutdown` behavior of `LoggerProvider` and `LogProcessor` [#1643](https://github.com/open-telemetry/opentelemetry-rust/pull/1643). |
108 | | - - `shutdown` can be called by any clone of the `LoggerProvider` without the need of waiting on all `Logger` drops. Thus, `try_shutdown` has been removed. |
| 112 | + - `shutdown` can be called by any clone of the `LoggerProvider` without the need of waiting on all `Logger` drops. Thus, `try_shutdown` has been removed. |
109 | 113 | - `shutdown` methods in `LoggerProvider` and `LogProcessor` now takes a immutable reference |
110 | 114 | - After `shutdown`, `LoggerProvider` will return noop `Logger` |
111 | 115 | - After `shutdown`, `LogProcessor` will not process any new logs |
|
0 commit comments