# Deprecated Scripts

These scripts have been moved here because their functionality is now handled by more comprehensive tools.

## Log Management Scripts (Superseded by log-manager.sh)

All of these scripts have been replaced by `scripts/log-manager.sh`, which provides:

- Real-time analysis with health scoring
- Performance monitoring with MEV-specific metrics
- Corruption detection and integrity validation
- Multi-channel alerting (email, Slack)
- Background monitoring daemon
- Operations dashboard generation
- Intelligent rotation (size and time-based)
- Advanced archiving with metadata

### Deprecated Scripts

1. **archive-logs.sh** → Use `./scripts/log-manager.sh archive`
2. **quick-archive.sh** → Use `./scripts/log-manager.sh full`
3. **view-latest-archive.sh** → Use `./scripts/log-manager.sh status`
4. **rotate-logs.sh** → Use `./scripts/log-manager.sh rotate`
5. **setup-log-rotation.sh** → Use `./scripts/log-manager.sh init`

## Migration Guide

**Instead of:**
```bash
./scripts/archive-logs.sh
```

**Use:**
```bash
./scripts/log-manager.sh archive
```

**Instead of:**
```bash
./scripts/quick-archive.sh --clear-logs
```

**Use:**
```bash
./scripts/log-manager.sh full
```

## Why These Were Deprecated

The individual log management scripts were created before the comprehensive `log-manager.sh` system was implemented. The new system provides:

- **Unified Interface**: Single command with multiple subcommands
- **Production Grade**: Health monitoring, alerting, and metrics
- **Better Maintenance**: One script to maintain instead of five
- **More Features**: Dashboard generation, daemon mode, performance tracking
- **Safer Operations**: Validation and corruption detection

## Can I Still Use These?

Yes, these scripts still work and are kept for backwards compatibility. However, it's recommended to migrate to `log-manager.sh` for better functionality and ongoing support.

## When Will These Be Removed?

These scripts will be kept for at least one major version release to allow for migration. They may be removed in a future version once all users have migrated to `log-manager.sh`.

---

**See:** `docs/SCRIPT_ANALYSIS_REPORT.md` for the full analysis