From 73526ec19f8cd26ccad328dc0b9693eff086ef9d Mon Sep 17 00:00:00 2001 From: Floris Bruynooghe Date: Wed, 25 Oct 2023 10:27:55 +0200 Subject: [PATCH] docs(tower): Mention how to enable http feature from sentry crate (#622) It is common to have this integration pulled in via the tower feature of the sentry crate. In this case it is convenient to know about the shortcut of the tower-http feature instead of having to add a direct dependency to sentry-tower. --- sentry-tower/src/lib.rs | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/sentry-tower/src/lib.rs b/sentry-tower/src/lib.rs index db9bb8b1..4cd9818d 100644 --- a/sentry-tower/src/lib.rs +++ b/sentry-tower/src/lib.rs @@ -105,9 +105,11 @@ //! //! ## Usage with `tower-http` //! -//! The `http` feature offers another layer which will attach request details -//! onto captured events, and optionally start a new performance monitoring -//! transaction based on the incoming HTTP headers. +//! The `http` feature of the `sentry-tower` crate offers another layer which will attach +//! request details onto captured events, and optionally start a new performance monitoring +//! transaction based on the incoming HTTP headers. When using the tower integration via +//! `sentry::integrations::tower`, this feature can also be enabled using the `tower-http` +//! feature of the `sentry` crate instead of the `tower` feature. //! //! The created transaction will automatically use the request URI as its name. //! This is sometimes not desirable in case the request URI contains unique IDs