Do errors and release artifacts have to leave together?
No. They have different jobs, so they get separate policies. Keep error reports on one schedule and hosted source maps and other release artifacts on another.
Keep what you need. Clear out the rest
Errors pile up. Release artifacts do too. Tell Telebugs how long to keep each one, and it automatically clears out the old stuff based on age, disk usage, or release count.
Can I keep the graph and lose the bulk?
Yes. A partial time-based cleanup removes old report data while preserving error graphs. Choose a full cleanup when you want the whole error to go.
What if my disk fills up first?
Set a fixed limit in gigabytes or a percentage of the whole disk. Telebugs removes the oldest errors first. For artifacts, it starts with the least-recently-used hosted maps, then artifacts from the oldest inactive releases, until usage is back below your limit.
What happens when I ship a new release?
Tell Telebugs how many releases to keep per project. When a new release arrives, artifacts beyond that window can be removed automatically.
Do I have to remember to run cleanup?
No. Cleanup runs nightly at 2 AM server time. Set your rules once and let Telebugs take it from there.