Attachments

Sentry can enrich your events for further investigation by storing additional files, such as config or log files, as attachments.

Creating Attachments

The simplest way to create an attachment is to use a path. The SDK will read the contents of the file each time it prepares an event or transaction, then adds the attachment to the same envelope. If the SDK can't read the file, the SDK logs an error message and drops the attachment.

#include "SentryAttachment.h"

const FString& Path = "your/path/file.log";
const FString& Filename = "file.log";

USentryAttachment* Attachment = NewObject<USentryAttachment>();
Attachment->InitializeWithPath(Path, Filename);

The same result can be achieved by calling the CreateSentryAttachmentWithPath function in blueprint.

Alternately, use bytes to initialize an attachment. When doing so, you also need to specify a filename.

#include "SentryAttachment.h"

const TArray<uint8>& Data = ...

const FString& Filename = "file.log";

USentryAttachment* Attachment = NewObject<USentryAttachment>();
Attachment->InitializeWithData(Data, Filename);

The same result can be achieved by calling the CreateSentryAttachmentWithData function in blueprint.

If your SDK supports offline caching, which is typical for mobile, each attachment is stored to disk for each event or transaction you capture when the device is offline. When using large attachments, this storage can consume the disk space if the device is offline for a longer time period. You can specify maximum attachment size to drop large attachments and avoid this issue.

In addition, you can set these parameters:

filename

The filename is the name of the file to display in Sentry. When using bytes you have to specify a filename, whereas with a path you don't as the SDK is going to use the last path component.

contentType

The type of content stored in this attachment. Any MIME type may be used; the default is application/octet-stream.

mimetype

The specific media content type that determines how the attachment is rendered in the Sentry UI. We currently support and can render the following MIME types:

• text/plain
• text/css
• text/csv
• text/html
• text/javascript
• text/json or text/x-json or application/json or application/ld+json
• image/jpeg
• image/png
• image/gif

Uploading Attachments

Attachments live on the Scope. You can either add an attachment on the global scope to be sent with every event or add it on the local Scope to just send the attachment with one specific event.

USentrySubsystem* SentrySubsystem = GEngine->GetEngineSubsystem<USentrySubsystem>();

FConfigureScopeDelegate ScopeDelegate;
ScopeDelegate.BindDynamic(this, &USomeClass::HandleScopeDelegate);

SentrySubsystem->ConfigureScope(ScopeDelegate);

// Put scope configuration logic here
void USomeClass::HandleScopeDelegate(USentryScope* Scope)
{
    USentryAttachment* Attachment = NewObject<USentryAttachment>();
    Attachment->InitializeWithPath("your/path/file.log", "file.log");

    Scope->AddAttachment(Attachment);
}

The same result can be achieved by calling the corresponding function in blueprint:

Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.

Learn more about how attachments impact your quota.

Access to Attachments

To limit access to attachments, navigate to your organization's General Settings, then select the Attachments Access dropdown to set appropriate access — any member of your organization, the organization billing owner, member, admin, manager, or owner.

By default, access is granted to all members when storage is enabled. If a member does not have access to the project, the ability to download an attachment is not available; the button will be greyed out in Sentry. The member may only view that an attachment is stored.

Viewing Attachments

Attachments display on the bottom of the Issue Details page for the event that is shown.

Alternately, attachments also appear in the Attachments tab on the Issue Details page, where you can view the Type of attachment, as well as associated events. Click the Event ID to open the Issue Details of that specific event.

Maximum Attachment Size

The scale is bytes and the default is 20 MiB. Please also check the maximum attachment size of Relay to make sure your attachments don't get discarded there.