Plex Guardian: Automated Database Integrity Monitoring #17

New Issue

peterwood · 2025-10-29T19:44:56-07:00

peterwood commented

2025-10-29 19:44:56 -07:00

Originally created by @acedanger on GitHub (May 29, 2025).

🔍 Plex Database Guardian - Automated Integrity Monitoring

Description

Implement automated Plex database integrity checking every 30 minutes to proactively detect and prevent database corruption issues.

Requirements

Automated Scanning: Database integrity check every 30 minutes via cron
Corruption Detection: Scan for database corruption and inconsistencies
Smart Monitoring: Avoid checks during active backup operations
Performance Optimization: Lightweight checks that don't impact Plex performance

Technical Implementation

SQLite Integrity Check: Use PRAGMA integrity_check for thorough validation
Quick Health Check: Fast consistency checks for frequent monitoring
Lock Detection: Check for database locks or blocked transactions
Size Monitoring: Track database size changes and growth patterns

Monitoring Schedule

# Every 30 minutes - Quick health check
*/30 * * * * /home/acedanger/shell/plex/check-plex-integrity.sh --quick

# Every 6 hours - Full integrity check  
0 */6 * * * /home/acedanger/shell/plex/check-plex-integrity.sh --full

# Daily - Comprehensive analysis with reporting
0 6 * * * /home/acedanger/shell/plex/check-plex-integrity.sh --comprehensive

Integration Points

Coordinate with existing backup scheduling to avoid conflicts
Integrate with current Plex monitoring infrastructure
Connect to auto-repair system (separate issue)
Use existing logging and notification systems

Output and Logging

JSON formatted results for machine parsing
Integration with existing performance logging
Structured logging for analysis and trending
Health status indicators for dashboard integration

Priority

🚨 Critical - System-breaking issues

Labels

critical
plex
database
monitoring
automation

Originally created by @acedanger on GitHub (May 29, 2025). # 🔍 Plex Database Guardian - Automated Integrity Monitoring ## Description Implement automated Plex database integrity checking every 30 minutes to proactively detect and prevent database corruption issues. ## Requirements - [ ] **Automated Scanning**: Database integrity check every 30 minutes via cron - [ ] **Corruption Detection**: Scan for database corruption and inconsistencies - [ ] **Smart Monitoring**: Avoid checks during active backup operations - [ ] **Performance Optimization**: Lightweight checks that don't impact Plex performance ## Technical Implementation - [ ] **SQLite Integrity Check**: Use `PRAGMA integrity_check` for thorough validation - [ ] **Quick Health Check**: Fast consistency checks for frequent monitoring - [ ] **Lock Detection**: Check for database locks or blocked transactions - [ ] **Size Monitoring**: Track database size changes and growth patterns ## Monitoring Schedule ```bash # Every 30 minutes - Quick health check */30 * * * * /home/acedanger/shell/plex/check-plex-integrity.sh --quick # Every 6 hours - Full integrity check 0 */6 * * * /home/acedanger/shell/plex/check-plex-integrity.sh --full # Daily - Comprehensive analysis with reporting 0 6 * * * /home/acedanger/shell/plex/check-plex-integrity.sh --comprehensive ``` ## Integration Points - [ ] Coordinate with existing backup scheduling to avoid conflicts - [ ] Integrate with current Plex monitoring infrastructure - [ ] Connect to auto-repair system (separate issue) - [ ] Use existing logging and notification systems ## Output and Logging - [ ] JSON formatted results for machine parsing - [ ] Integration with existing performance logging - [ ] Structured logging for analysis and trending - [ ] Health status indicators for dashboard integration ## Priority 🚨 Critical - System-breaking issues ## Labels - critical - plex - database - monitoring - automation

peterwood added the critical database automation monitoring plex labels 2025-10-29 19:44:56 -07:00

peterwood referenced this issue

2025-10-29 19:44:57 -07:00

Plex Guardian: TUI Dashboard Interface #20

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: peterwood/shell#17