getsentry / getsentry/self-hosted

How to handle disk space usage of debug files

Open
#3,157 6 comments 0 reactions 0 assignees View on GitHub
Feature
Dominant language
Shell
Stars
9.6k
Forks
2k
Avg merge
1d 3h
Merged PRs (30d)
12

Description

### Problem Statement

I build for 3 Unity platforms, and the debug files that gets uploaded per platform is over 1gb. So per build that is over 3gb of debug files that gets uploaded.

I typically do beta builds around once a day or so. Which adds up to over 100gb of debug files per month.

What are my options for handling this? I only really care about the most recent beta and production debug files, and not previous builds.

### Solution Brainstorm

_No response_

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are mentioned. First clarify whether the desired outcome is documentation, configurable retention, or cleanup of old debug files; completion criteria are not specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
unity
Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.