Clear all debug files
DELETE /api/system/debug/clear-all
Clear ALL debug files from the system (use with extreme caution).
Performs complete cleanup of all debug files regardless of age. This is a destructive operation intended for fresh starts or when debug files are no longer needed for troubleshooting.
⚠️ WARNING: This operation is irreversible!
- Deletes ALL crashdata and dumplog files
- No age-based filtering or retention
- Cannot be undone once executed
- Should only be used when debug data is no longer needed
Returns:
status: Operation status (“success” or “error”)message: Human-readable operation summaryfiles_deleted: Total count of files deletedspace_freed_mb: Total disk space freed in megabytesfiles_kept: Always 0 (all files deleted)details: List of deleted filenames with sizes (first 10)
Deletion Process:
- Identifies all recognized debug file types
- Calculates total size before deletion
- Safely deletes each file with error handling
- Continues deletion even if individual files fail
- Logs all deletion operations for audit trail
- Reports total space freed
File Types Deleted:
- crashdata-*.json - Crash dump data files
- dumplog-*.txt - Dump log files
- *.dump - Generic dump files
- *.crash - Generic crash files
Safety Features:
- Only deletes recognized debug file types
- Never deletes files from other directories
- Continues operation even if individual deletions fail
- Comprehensive error logging for failed operations
- Detailed reporting of deletion results
Use Cases:
- Fresh start after resolving persistent issues
- Clearing space after debugging is complete
- Preparing for production deployment
- Regular maintenance when debug data is no longer relevant
Raises:
- HTTPException (500): If deletion operation fails completely
Example Response:
{
"status": "success",
"message": "Cleared all debug files. Deleted 42 files.",
"files_deleted": 42,
"space_freed_mb": 125.67,
"files_kept": 0,
"details": [
"crashdata-2024-12-18T10-30-00-000Z.json (3.2 MB)",
"dumplog-2024-12-18T14-20-00-000Z.txt (2.1 MB)"
]
}Responses
Section titled “ Responses ”Successful Response
Response model for debug cleanup operations.
Provides comprehensive cleanup results including deletion counts, disk space freed, retention counts, and detailed file listings. Used by debug cleanup endpoints to report cleanup operation results with full transparency.
Fields: status: Operation status (“success”, “error”, “partial”) message: Human-readable operation summary files_deleted: Count of files successfully deleted space_freed_mb: Total disk space freed in megabytes files_kept: Count of files preserved based on retention policy details: List of deleted filenames with sizes (limited to first 10)
Example:
json { "status": "success", "message": "Cleanup complete. Deleted 15 files older than 7 days. Kept 8 recent files.", "filesDeleted": 15, "spaceFreedMb": 42.35, "filesKept": 8, "details": [ "crashdata-2024-12-01T10-30-00-000Z.json (2.5 MB)", "dumplog-2024-12-02T14-20-00-000Z.txt (1.8 MB)" ] }