|
1 | | -[](https://crates.io/crates/opentelemetry-application-insights) |
2 | | -[](https://docs.rs/opentelemetry-application-insights) |
| 1 | +[](https://crates.io/crates/opentelemetry-application-insights) |
| 2 | +[](https://docs.rs/opentelemetry-application-insights) |
3 | 3 | [](https://github.com/frigus02/opentelemetry-application-insights/actions?query=workflow%3A%22CI%22) |
4 | 4 |
|
5 | 5 | # opentelemetry-application-insights |
@@ -61,16 +61,17 @@ async fn main() { |
61 | 61 | ### Features |
62 | 62 |
|
63 | 63 | In order to support different async runtimes, the exporter requires you to specify an HTTP |
64 | | -client that works with your chosen runtime. This crate comes with support for: |
| 64 | +client that works with your chosen runtime. The [`opentelemetry-http`] crate comes with support |
| 65 | +for: |
65 | 66 |
|
66 | 67 | - [`surf`] for [`async-std`]: enable the **surf-client** and **opentelemetry/rt-async-std** |
67 | 68 | features and configure the exporter with `with_client(surf::Client::new())`. |
68 | | -- [`reqwest`] for [`tokio`]: enable the **reqwest-client** and **opentelemetry/rt-tokio** features |
69 | | - and configure the exporter with `with_client(reqwest::Client::new())`. |
70 | | -- [`reqwest`] for synchronous exports: enable the **reqwest-blocking-client** feature and |
71 | | - configure the exporter with `with_client(reqwest::blocking::Client::new())`. |
| 69 | +- [`reqwest`] for [`tokio`]: enable the **reqwest-client** and **opentelemetry/rt-tokio** |
| 70 | + features and configure the exporter with either `with_client(reqwest::Client::new())` or |
| 71 | + `with_client(reqwest::blocking::Client::new())`. |
72 | 72 |
|
73 | 73 | [`async-std`]: https://crates.io/crates/async-std |
| 74 | +[`opentelemetry-http`]: https://crates.io/crates/opentelemetry-http |
74 | 75 | [`reqwest`]: https://crates.io/crates/reqwest |
75 | 76 | [`surf`]: https://crates.io/crates/surf |
76 | 77 | [`tokio`]: https://crates.io/crates/tokio |
|
0 commit comments