Environment
Version: 0.36.0
Sentry set up with the sentry-tracing integration.
Steps to Reproduce
- Followed instructions in the docs to track errors using the
tracing macros: https://docs.rs/sentry-tracing/0.36.0/sentry_tracing/#tracking-errors
- Logged an error along the lines of
tracing::error!(error = &custom_error as &dyn Error, "my operation failed - ...");
- tried with
let custom_error = std::io::Error::new(std::io::ErrorKind::Other, "Custom ioErrorKind Other Error");
- tried with custom
thiserror based error struct
- Logged a "control" error using
error!("my operation failed - simple error!(\"my operation failed\") has helpful title");
Expected Result
Errors to show up in Sentry with a useful title, either based on the original message, or some version of the error struct name
Actual Result
In the Sentry dashboard, the errors reported using the error = capturing method had titles that had nothing to do with the error but rather referenced the tracing crate. Errors reported without the error = capturing method show up with the message in the title.

Environment
Version:
0.36.0Sentry set up with the
sentry-tracingintegration.Steps to Reproduce
tracingmacros: https://docs.rs/sentry-tracing/0.36.0/sentry_tracing/#tracking-errorstracing::error!(error = &custom_error as &dyn Error, "my operation failed - ...");let custom_error = std::io::Error::new(std::io::ErrorKind::Other, "Custom ioErrorKind Other Error");thiserrorbased error structerror!("my operation failed - simple error!(\"my operation failed\") has helpful title");Expected Result
Errors to show up in Sentry with a useful title, either based on the original message, or some version of the error struct name
Actual Result
In the Sentry dashboard, the errors reported using the
error =capturing method had titles that had nothing to do with the error but rather referenced thetracingcrate. Errors reported without theerror =capturing method show up with the message in the title.