Symbol Servers

BugSplat can process crashes using symbol files stored in external symbol servers. BugSplat supports accessing HTTP/HTTPS servers and Amazon S3 Buckets. BugSplat caches files from external symbol servers, ensuring fast crash calculation. Please note that if BugSplat requests a file not present on your external symbol server, it will not try to access the file again for 24 hours.

HTTP

BugSplat can access symbol files over HTTP and HTTPS. This method also supports Windows SymStore/SymProxy symbol servers. To connect an HTTP symbol server to BugSplat, navigate to the Symbols page. Click the + Add Server button, add a URL value, and click OK.

Adding an External HTTP Symbol Server

AWS S3

For AWS S3 symbol servers, you'll want to create a minimally permissive IAM User so that BugSplat can access your S3 bucket. Modify this example policy and attach it to your newly created IAM User.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:ListBucket"
            ],
            "Resource": [
                "arn:aws:s3:::{your-s3-bucket}",
                "arn:aws:s3:::{your-s3-bucket}/*"
            ]
        }
    ]
}

Once you create your IAM user, generate an access key/secret to allow BugSplat to access your S3 bucket. Navigate to the Symbols page and click + Add Server. Select AWS-S3 in the Type dropdown. Enter values for URL, Region, Access Key, Secret Key, and click OK.

Adding an External S3 Symbol Server