<p align="center">
<a href="https://sentry.io/?utm_source=github&utm_medium=logo" target="_blank">
<img src="https://sentry-brand.storage.googleapis.com/sentry-wordmark-dark-280x84.png" alt="Sentry" width="280" height="84">
</a>
</p>
# Sentry Rust SDK: sentry-tower
Adds support for automatic hub binding for each request received by the Tower server (or client,
though usefulness is limited in this case).
This allows breadcrumbs collected during the request handling to land in a specific hub, and
avoid having them mixed across requests should a new hub be bound at each request.
## Examples
```rust
use sentry_tower::NewSentryLayer;
// Compose a Tower service where each request gets its own Sentry hub
let service = ServiceBuilder::new()
.layer(NewSentryLayer::<Request>::new_from_top())
.timeout(Duration::from_secs(30))
.service(tower::service_fn(|req: Request| format!("hello {}", req)));
```
More customization can be achieved through the `new` function, such as passing a [`Hub`]
directly.
```rust
use sentry::Hub;
use sentry_tower::SentryLayer;
// Create a hub dedicated to web requests
// Compose a Tower service
let service = ServiceBuilder::new()
.layer(SentryLayer::<_, _, Request>::new(hub))
.timeout(Duration::from_secs(30))
.service(tower::service_fn(|req: Request| format!("hello {}", req)));
```
The layer can also accept a closure to return a hub depending on the incoming request.
```rust
use sentry::Hub;
use sentry_tower::SentryLayer;
// Compose a Tower service
let service = ServiceBuilder::new()
.layer(SentryLayer::new(|req: &Request| match req.as_str() {
"hello" => hello.clone(),
_ => other.clone(),
}))
.timeout(Duration::from_secs(30))
.service(tower::service_fn(|req: Request| format!("{} world", req)));
```
When using Tonic, the layer can be used directly by the Tonic stack:
```rust
use hello_world::{greeter_server::*, *};
use sentry_tower::NewSentryLayer;
struct GreeterService;
#[tonic::async_trait]
impl Greeter for GreeterService {
async fn say_hello(
&self,
req: Request<HelloRequest>,
) -> Result<Response<HelloReply>, Status> {
let HelloRequest { name } = req.into_inner();
if name == "world" {
capture_anyhow(&anyhow!("Trying to greet a planet"));
return Err(Status::invalid_argument("Cannot greet a planet"));
}
Ok(Response::new(HelloReply {
message: format!("Hello {}", name),
}))
}
}
Server::builder()
.layer(NewSentryLayer::new_from_top())
.add_service(GreeterServer::new(GreeterService))
.serve("127.0.0.1:50051".parse().unwrap())
.await?;
```
### Usage with `tower-http`
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
or similar. In this case, users should manually override the transaction name
in the request handler using the [`Scope::set_transaction`](https://docs.rs/sentry-tower/0.34.0/sentry_tower/sentry_core::Scope::set_transaction)
method.
When combining both layers, take care of the ordering of both. For example
with [`tower::ServiceBuilder`], always define the `Hub` layer before the `Http`
one, like so:
```rust
let layer = tower::ServiceBuilder::new()
.layer(sentry_tower::NewSentryLayer::<Request>::new_from_top())
.layer(sentry_tower::SentryHttpLayer::with_transaction());
```
[`tower::ServiceBuilder`]: https://docs.rs/tower/latest/tower/struct.ServiceBuilder.html
## Resources
License: Apache-2.0
- [Discord](https://discord.gg/ez5KZN7) server for project discussions.
- Follow [@getsentry](https://twitter.com/getsentry) on Twitter for updates