Rails’s Active Storage component generates the following ActiveSupport::Notifications events:
service_upload.active_storageservice_download.active_storageservice_streaming_download.active_storageservice_download_chunk.active_storageservice_delete.active_storageservice_delete_prefixed.active_storageservice_exist.active_storageservice_url.active_storageservice_mirror.active_storageservice_update_metadata.active_storagepreview.active_storageanalyze.active_storage
More on these events is available here. All are worth tracing, except maybe service_url, as they’re likely to be responsible for a significant portion of runtime in transactions where they occur. For example, here’s a request in Sentry where uploading to S3 takes the majority of the total duration but isn’t represented:
I think this should be relatively straightforward using the existing subscriber system in sentry-rails.
Rails’s Active Storage component generates the following
ActiveSupport::Notificationsevents:service_upload.active_storageservice_download.active_storageservice_streaming_download.active_storageservice_download_chunk.active_storageservice_delete.active_storageservice_delete_prefixed.active_storageservice_exist.active_storageservice_url.active_storageservice_mirror.active_storageservice_update_metadata.active_storagepreview.active_storageanalyze.active_storageMore on these events is available here. All are worth tracing, except maybe
service_url, as they’re likely to be responsible for a significant portion of runtime in transactions where they occur. For example, here’s a request in Sentry where uploading to S3 takes the majority of the total duration but isn’t represented:I think this should be relatively straightforward using the existing subscriber system in
sentry-rails.