You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updates the opentelemetry-otlp crate to allow users to configure TLS
using environment variables. Removing the need to crating the TLS config
object and defining it with the `with_tls_config` method. In the same
way other OTLP libraries does (e.g. go lang).
Signed-off-by: José Guilherme Vanz <jguilhermevanz@suse.com>
partially to properly handle `shutdown()` when using `http`. (`tonic` still
21
22
does not do proper shutdown)
22
-
-*Breaking*
23
-
ExporterBuilder's build() method now Result with `ExporterBuildError` being the
24
-
Error variant. Previously it returned signal specific errors like `LogError`
25
-
from the `opentelemetry_sdk`, which are no longer part of the sdk. No changes
26
-
required if you were using unwrap/expect. If you were matching on the returning
27
-
Error enum, replace with the enum `ExporterBuildError`. Unlike the previous
28
-
`Error` which contained many variants unrelated to building an exporter, the
29
-
new one returns specific variants applicable to building an exporter. Some
30
-
variants might be applicable only on select features.
31
-
Also, now unused `Error` enum is removed.
23
+
-_Breaking_
24
+
ExporterBuilder's build() method now Result with `ExporterBuildError` being the
25
+
Error variant. Previously it returned signal specific errors like `LogError`
26
+
from the `opentelemetry_sdk`, which are no longer part of the sdk. No changes
27
+
required if you were using unwrap/expect. If you were matching on the returning
28
+
Error enum, replace with the enum `ExporterBuildError`. Unlike the previous
29
+
`Error` which contained many variants unrelated to building an exporter, the
30
+
new one returns specific variants applicable to building an exporter. Some
31
+
variants might be applicable only on select features.
32
+
Also, now unused `Error` enum is removed.
32
33
-**Breaking**`ExportConfig`'s `timeout` field is now optional(`Option<Duration>`)
33
34
-**Breaking** Export configuration done via code is final. ENV variables cannot be used to override the code config.
34
35
Do not use code based config, if there is desire to control the settings via ENV variables.
@@ -58,10 +59,10 @@ Released 2025-Feb-10
58
59
- The HTTP clients (reqwest, reqwest-blocking, hyper) now support the
59
60
export timeout interval configured in below order
60
61
- Signal specific env variable `OTEL_EXPORTER_OTLP_TRACES_TIMEOUT`,
61
-
`OTEL_EXPORTER_OTLP_LOGS_TIMEOUT` or `OTEL_EXPORTER_OTLP_TIMEOUT`.
62
+
`OTEL_EXPORTER_OTLP_LOGS_TIMEOUT` or `OTEL_EXPORTER_OTLP_TIMEOUT`.
62
63
-`OTEL_EXPORTER_OTLP_TIMEOUT` env variable.
63
64
-`with_http().with_timeout()` API method of
64
-
`LogExporterBuilder` and `SpanExporterBuilder` and `MetricsExporterBuilder`.
65
+
`LogExporterBuilder` and `SpanExporterBuilder` and `MetricsExporterBuilder`.
65
66
- The default interval of 10 seconds is used if none is configured.
66
67
67
68
## 0.27.0
@@ -74,6 +75,7 @@ Released 2024-Nov-11
74
75
- Update `opentelemetry-proto` dependency version to 0.27
75
76
76
77
-**BREAKING**:
78
+
77
79
- ([#2217](https://github.com/open-telemetry/opentelemetry-rust/pull/2217)) **Replaced**: The `MetricsExporterBuilder` interface is modified from `with_temporality_selector` to `with_temporality` example can be seen below:
Pullrequest [#2221](https://github.com/open-telemetry/opentelemetry-rust/pull/2221) has a detailed migration guide in the description. See example below,
91
94
and [basic-otlp](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/examples/basic-otlp/src/main.rs) for more details:
nowuse `.with_resource(RESOURCE::default())` to configure Resource when using
170
+
`OtlpLogPipeline`.
162
171
-**Breaking**The methods `OtlpTracePipeline::install_simple()` and `OtlpTracePipeline::install_batch()` would now return `TracerProvider` instead of `Tracer`.
163
172
These methods would also no longer set the global tracer provider.It would now be the responsibility of users to set it by calling `global::set_tracer_provider(tracer_provider.clone());`.Refertothe [basic-otlp](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/examples/basic-otlp/src/main.rs) and [basic-otlp-http](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/examples/basic-otlp-http/src/main.rs) examples on how to initialize OTLP Trace Exporter.
`Logger`.Refertothe [basic-otlp](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/examples/basic-otlp/src/main.rs) and [basic-otlp-http](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/examples/basic-otlp-http/src/main.rs) examples for how to initialize OTLP Log Exporter to use with OpenTelemetryLogBridge and OpenTelemetryTracingBridge respectively.
`Logger`.Refertothe [basic-otlp](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/examples/basic-otlp/src/main.rs) and [basic-otlp-http](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-otlp/examples/basic-otlp-http/src/main.rs) examples for how to initialize OTLP Log Exporter to use with OpenTelemetryLogBridge and OpenTelemetryTracingBridge respectively.
0 commit comments