|
4 | 4 |
|
5 | 5 | # Dynatrace |
6 | 6 |
|
7 | | -*This is the last release of the crate!* |
| 7 | +The final release of this crate was 0.4.0. Dynatrace now recommends using the OTLP exporter. They also provide a [migration guide] |
| 8 | +For an example on how to configure the OTLP exporter in a Rust application, check out the [Rust integration walk-through] page in the Dynatrace documentation. |
8 | 9 |
|
9 | | -[Dynatrace](https://www.dynatrace.com/integrations/opentelemetry) supports native |
10 | | -OpenTelemetry protocol (OTLP) ingest for traces, metrics and logs. |
11 | | -All signals can be sent directly to Dynatrace via **OTLP protobuf over HTTP** |
12 | | -using the built-in OTLP/HTTP Exporter available in the OpenTelemetry Rust SDK. |
13 | | -More information on configuring your Rust applications to use the OTLP exporter can be found in the |
14 | | -[Dynatrace documentation](https://www.dynatrace.com/support/help/shortlink/otel-wt-rust). |
| 10 | +[migration guide]: https://www.dynatrace.com/support/help/shortlink/migrating-dynatrace-metrics-exporter-otlp-exporter#migrate-applications |
| 11 | +[Rust integration walk-through]: https://www.dynatrace.com/support/help/shortlink/otel-wt-rust |
15 | 12 |
|
16 | | -## Dynatrace OpenTelemetry Metrics Exporter for Rust |
17 | 13 |
|
18 | | - |
19 | | -[](https://crates.io/crates/opentelemetry-dynatrace) |
20 | | -[](https://docs.rs/opentelemetry-dynatrace) |
21 | | -[](./LICENSE) |
22 | | -[](https://github.com/open-telemetry/opentelemetry-rust/actions?query=workflow%3ACI+branch%3Amain) |
23 | | -[](https://cloud-native.slack.com/archives/C03GDP0H023) |
| 14 | +## Notice Removal |
24 | 15 |
|
25 | | -> **Warning** |
26 | | -> Dynatrace supports native OpenTelemetry protocol (OTLP) ingest for traces, metrics and logs. |
27 | | -> Therefore, the proprietary Dynatrace OpenTelemetry metrics exporter is deprecated in favor of exporting via OTLP/HTTP. |
28 | | -> |
29 | | -> The exporter is still available but after the end of 2023, no support, updates, or compatibility with newer OTel versions will be provided. |
30 | | -> |
31 | | -> Please refer to the [migration guide](https://www.dynatrace.com/support/help/shortlink/migrating-dynatrace-metrics-exporter-otlp-exporter#migrate-applications) for instructions on how to migrate to the OTLP HTTP exporter, as well as reasoning and benefits for this transition. |
32 | | -> |
33 | | -> For an example on how to configure the OTLP exporter in a Rust application, check out the [Rust integration walk-through](https://www.dynatrace.com/support/help/shortlink/otel-wt-rust) page in the Dynatrace documentation. |
34 | | -
|
35 | | -### Overview |
36 | | - |
37 | | -[`OpenTelemetry`] is a collection of tools, APIs, and SDKs used to instrument, |
38 | | -generate, collect, and export telemetry data (metrics, logs, and traces) for |
39 | | -analysis in order to understand your software's performance and behavior. This |
40 | | -crate provides additional propagators and exporters for sending telemetry data |
41 | | -to [`Dynatrace`]. |
42 | | - |
43 | | -### Exporter features |
44 | | - |
45 | | -* **Metrics** - Ingest metric data to Dynatrace using the [Dynatrace Metrics ingestion protocol]. |
46 | | - |
47 | | -This exporter only supports the ingestion of metric data. For trace data, use |
48 | | -[`opentelemetry-otlp`] as described in the |
49 | | -[Dynatrace documentation for Rust]. This exporter is based on the OpenTelemetry |
50 | | -Metrics SDK for Rust, which is currently in an alpha state and neither |
51 | | -considered stable nor complete as of this writing. As such, this exporter is |
52 | | -not intended for production use until the underlying OpenTelemetry Metrics API |
53 | | -and SDK are stable. See [`open-telemetry/opentelemetry-rust`] for the current |
54 | | -state of the OpenTelemetry SDK for Rust. |
55 | | - |
56 | | -[Dynatrace]: https://www.dynatrace.com/ |
57 | | -[Dynatrace Metrics ingestion protocol]: https://www.dynatrace.com/support/help/how-to-use-dynatrace/metrics/metric-ingestion/metric-ingestion-protocol/ |
58 | | -[Dynatrace documentation for Rust]: https://www.dynatrace.com/support/help/shortlink/opent-rust |
59 | | -[`open-telemetry/opentelemetry-rust`]: https://github.com/open-telemetry/opentelemetry-rust |
60 | | - |
61 | | -#### Examples |
62 | | - |
63 | | -The examples directory contains an [advanced example](../examples/dynatrace) |
64 | | -showing the ingestion of trace data and metric data together. |
65 | | - |
66 | | -[`opentelemetry-otlp`]: https://crates.io/crates/opentelemetry-otlp |
67 | | -[`opentelemetry-dynatrace`]: https://crates.io/crates/opentelemetry-dynatrace |
68 | | - |
69 | | -### Performance |
70 | | - |
71 | | -For optimal performance, a batch exporter is used. You can enable the `rt-tokio` |
72 | | -feature flag to use the [`tokio`] runtime, or enable the `rt-async-std` feature |
73 | | -flag to use the [`async-std`] runtime to have a batch exporter configured for |
74 | | -you automatically. |
75 | | - |
76 | | -[`tokio`]: https://tokio.rs |
77 | | -[`async-std`]: https://async.rs |
78 | | - |
79 | | -### Choosing an HTTP client |
80 | | - |
81 | | -The HTTP client that this exporter will use can be overridden with feature |
82 | | -flags. By default the `reqwest-client` feature flag is enabled which will use |
83 | | -the [`reqwest`] http client. |
84 | | - |
85 | | -- `reqwest-client` (enabled by default): use the [`reqwest`] http client to send metric data. |
86 | | -- `reqwest-tls` (enabled by default): use the [`reqwest`] http client with [`rustls`] to enable TLS support. |
87 | | -- `reqwest-blocking-client`: use the [`reqwest`] blocking http client to send metric data. |
88 | | -- `isahc-client`: use the [`isahc`] http client to send metric data. |
89 | | -- `surf-client`: use the [`surf`] http client to send metric data. |
90 | | - |
91 | | -You can also configure your own http client implementation using the `HttpClient` trait. |
92 | | - |
93 | | -[`reqwest`]: https://docs.rs/reqwest/latest/reqwest/ |
94 | | -[`rustls`]: https://docs.rs/rustls/latest/rustls/ |
95 | | -[`isahc`]: https://docs.rs/isahc/latest/isahc/ |
96 | | -[`surf`]: https://docs.rs/surf/latest/surf/ |
97 | | - |
98 | | -### WebAssembly |
99 | | - |
100 | | -WebAssembly support can be enabled with the `wasm` feature flag. |
101 | | - |
102 | | -[`Dynatrace`]: https://www.dynatrace.com/ |
103 | | -[`OpenTelemetry`]: https://crates.io/crates/opentelemetry |
| 16 | +This README and directory can be removed after any time in 2024 at least 6 months from the last release date of `opentelemetry-dynatrace`. |
0 commit comments