You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is relevant for the actix and tower-http integrations. We have no integration for outgoing requests so that is the responsibility of the API user.
When we do HTTP requests to third party services we create a breadcrumb with the URL and also create a span that has the URL as a description (and also breadcrumbs including this URL are created.)
I believe this is relevant for the actix and tower-http integrations. We have no integration for outgoing requests so that is the responsibility of the API user.
Copy-pasted: getsentry/sentry-python#1742
When we do HTTP requests to third party services we create a breadcrumb with the URL and also create a span that has the URL as a description (and also breadcrumbs including this URL are created.)
We created RFC-0038 to decide how to improve the current situation and creating a spec here: getsentry/develop#773
Make sure that all integrations that record outgoing or incoming HTTP request structure the data like described in the spec linked above.
The text was updated successfully, but these errors were encountered: