-
Notifications
You must be signed in to change notification settings - Fork 692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Add reqwest-tracing to related crates in README #2331
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding your crate!
There's also a copy of the same list in the lib.rs
docs for the tracing
crate, here:
Lines 770 to 812 in 1215ab2
//! Additionally, there are also several third-party crates which are not | |
//! maintained by the `tokio` project. These include: | |
//! | |
//! - [`tracing-timing`] implements inter-event timing metrics on top of `tracing`. | |
//! It provides a subscriber that records the time elapsed between pairs of | |
//! `tracing` events and generates histograms. | |
//! - [`tracing-opentelemetry`] provides a subscriber for emitting traces to | |
//! [OpenTelemetry]-compatible distributed tracing systems. | |
//! - [`tracing-honeycomb`] Provides a layer that reports traces spanning multiple machines to [honeycomb.io]. Backed by [`tracing-distributed`]. | |
//! - [`tracing-distributed`] Provides a generic implementation of a layer that reports traces spanning multiple machines to some backend. | |
//! - [`tracing-actix-web`] provides `tracing` integration for the `actix-web` web framework. | |
//! - [`tracing-actix`] provides `tracing` integration for the `actix` actor | |
//! framework. | |
//! - [`tracing-gelf`] implements a subscriber for exporting traces in Greylog | |
//! GELF format. | |
//! - [`tracing-coz`] provides integration with the [coz] causal profiler | |
//! (Linux-only). | |
//! - [`tracing-bunyan-formatter`] provides a layer implementation that reports events and spans | |
//! in [bunyan] format, enriched with timing information. | |
//! - [`tracing-wasm`] provides a `Collect`/`Subscribe` implementation that reports | |
//! events and spans via browser `console.log` and [User Timing API (`window.performance`)]. | |
//! - [`tracing-web`] provides a layer implementation of level-aware logging of events | |
//! to web browsers' `console.*` and span events to the [User Timing API (`window.performance`)]. | |
//! - [`tide-tracing`] provides a [tide] middleware to trace all incoming requests and responses. | |
//! - [`test-log`] takes care of initializing `tracing` for tests, based on | |
//! environment variables with an `env_logger` compatible syntax. | |
//! - [`tracing-unwrap`] provides convenience methods to report failed unwraps | |
//! on `Result` or `Option` types to a [`collect`]. | |
//! - [`diesel-tracing`] provides integration with [`diesel`] database connections. | |
//! - [`tracing-tracy`] provides a way to collect [Tracy] profiles in instrumented | |
//! applications. | |
//! - [`tracing-elastic-apm`] provides a layer for reporting traces to [Elastic APM]. | |
//! - [`tracing-etw`] provides a layer for emitting Windows [ETW] events. | |
//! - [`tracing-fluent-assertions`] provides a fluent assertions-style testing | |
//! framework for validating the behavior of `tracing` spans. | |
//! - [`sentry-tracing`] provides a layer for reporting events and traces to [Sentry]. | |
//! - [`tracing-forest`] provides a subscriber that preserves contextual coherence by | |
//! grouping together logs from the same spans during writing. | |
//! - [`tracing-loki`] provides a layer for shipping logs to [Grafana Loki]. | |
//! - [`tracing-logfmt`] provides a layer that formats events and spans into the logfmt format. | |
//! | |
//! If you're the maintainer of a `tracing` ecosystem crate not listed above, | |
//! please let us know! We'd love to add your project to the list! |
would you mind adding a link there as well? Thanks!
(we really should get around to using #[doc = include_str!(...)]
to avoid having to duplicate stuff between the README and lib docs...)
450b969
to
ba2d0c8
Compare
Thanks @hawkw, added the crate to the module docs and committed your suggestions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, this looks good to me!
# 0.1.37 (October 6, 2022) This release of `tracing` incorporates changes from `tracing-core` [v0.1.30][core-0.1.30] and `tracing-attributes` [v0.1.23][0.1.23], including the new `Subscriber::on_register_dispatch` method for performing late initialization after a `Subscriber` is registered as a `Dispatch`, and bugfixes for the `#[instrument]` attribute. Additionally, it fixes instances of the `bare_trait_objects` lint, which is now a warning on `tracing`'s MSRV and will become an error in the next edition. ### Fixed - **attributes**: Incorrect handling of inner attributes in `#[instrument]`ed functions (#2307) - **attributes**: Incorrect location of compiler diagnostic spans generated for type errors in `#[instrument]`ed `async fn`s (#2270) - **attributes**: Updated `syn` dependency to fix compilation with `-Z minimal-versions` (#2246) - `bare_trait_objects` warning in `valueset!` macro expansion (#2308) ### Added - **core**: `Subscriber::on_register_dispatch` method (#2269) - **core**: `WeakDispatch` type and `Dispatch::downgrade()` function (#2293) ### Changed - `tracing-core`: updated to [0.1.30][core-0.1.30] - `tracing-attributes`: updated to [0.1.23][attrs-0.1.23] ### Documented - Added [`tracing-web`] and [`reqwest-tracing`] to related crates (#2283], [#2331) Thanks to new contributors @compiler-errors, @e-nomem, @WorldSEnder, @Xiami2012, and @tl-rodrigo-gryzinski, as well as @jswrenn and @CAD97, for contributing to this release! [core-0.1.30]: https://github.com/tokio-rs/tracing/releases/tag/tracing-core-0.1.30 [attrs-0.1.23]: https://github.com/tokio-rs/tracing/releases/tag/tracing-attributes-0.1.23 [`tracing-web`]: https://crates.io/crates/tracing-web/ [`reqwest-tracing`]: https://crates.io/crates/reqwest-tracing/
# 0.1.37 (October 6, 2022) This release of `tracing` incorporates changes from `tracing-core` [v0.1.30][core-0.1.30] and `tracing-attributes` [v0.1.23][attrs-0.1.23], including the new `Subscriber::on_register_dispatch` method for performing late initialization after a `Subscriber` is registered as a `Dispatch`, and bugfixes for the `#[instrument]` attribute. Additionally, it fixes instances of the `bare_trait_objects` lint, which is now a warning on `tracing`'s MSRV and will become an error in the next edition. ### Fixed - **attributes**: Incorrect handling of inner attributes in `#[instrument]`ed functions (#2307) - **attributes**: Incorrect location of compiler diagnostic spans generated for type errors in `#[instrument]`ed `async fn`s (#2270) - **attributes**: Updated `syn` dependency to fix compilation with `-Z minimal-versions` (#2246) - `bare_trait_objects` warning in `valueset!` macro expansion (#2308) ### Added - **core**: `Subscriber::on_register_dispatch` method (#2269) - **core**: `WeakDispatch` type and `Dispatch::downgrade()` function (#2293) ### Changed - `tracing-core`: updated to [0.1.30][core-0.1.30] - `tracing-attributes`: updated to [0.1.23][attrs-0.1.23] ### Documented - Added [`tracing-web`] and [`reqwest-tracing`] to related crates (#2283, #2331) Thanks to new contributors @compiler-errors, @e-nomem, @WorldSEnder, @Xiami2012, and @tl-rodrigo-gryzinski, as well as @jswrenn and @CAD97, for contributing to this release! [core-0.1.30]: https://github.com/tokio-rs/tracing/releases/tag/tracing-core-0.1.30 [attrs-0.1.23]: https://github.com/tokio-rs/tracing/releases/tag/tracing-attributes-0.1.23 [`tracing-web`]: https://crates.io/crates/tracing-web/ [`reqwest-tracing`]: https://crates.io/crates/reqwest-tracing/
# 0.1.37 (October 6, 2022) This release of `tracing` incorporates changes from `tracing-core` [v0.1.30][core-0.1.30] and `tracing-attributes` [v0.1.23][attrs-0.1.23], including the new `Subscriber::on_register_dispatch` method for performing late initialization after a `Subscriber` is registered as a `Dispatch`, and bugfixes for the `#[instrument]` attribute. Additionally, it fixes instances of the `bare_trait_objects` lint, which is now a warning on `tracing`'s MSRV and will become an error in the next edition. ### Fixed - **attributes**: Incorrect handling of inner attributes in `#[instrument]`ed functions (tokio-rs#2307) - **attributes**: Incorrect location of compiler diagnostic spans generated for type errors in `#[instrument]`ed `async fn`s (tokio-rs#2270) - **attributes**: Updated `syn` dependency to fix compilation with `-Z minimal-versions` (tokio-rs#2246) - `bare_trait_objects` warning in `valueset!` macro expansion (tokio-rs#2308) ### Added - **core**: `Subscriber::on_register_dispatch` method (tokio-rs#2269) - **core**: `WeakDispatch` type and `Dispatch::downgrade()` function (tokio-rs#2293) ### Changed - `tracing-core`: updated to [0.1.30][core-0.1.30] - `tracing-attributes`: updated to [0.1.23][attrs-0.1.23] ### Documented - Added [`tracing-web`] and [`reqwest-tracing`] to related crates (tokio-rs#2283, tokio-rs#2331) Thanks to new contributors @compiler-errors, @e-nomem, @WorldSEnder, @Xiami2012, and @tl-rodrigo-gryzinski, as well as @jswrenn and @CAD97, for contributing to this release! [core-0.1.30]: https://github.com/tokio-rs/tracing/releases/tag/tracing-core-0.1.30 [attrs-0.1.23]: https://github.com/tokio-rs/tracing/releases/tag/tracing-attributes-0.1.23 [`tracing-web`]: https://crates.io/crates/tracing-web/ [`reqwest-tracing`]: https://crates.io/crates/reqwest-tracing/
Add
reqwest-tracing
to the list of related crates.