Agents SSH Targets EBS Validation Proxy Self-Test Agent Upgrades

🔐 Admin access required

Sign in with an admin account to access this page.

Sign In

# Proxy Self-Test

Validate the full EBS proxy ingestion pipeline — parse → score → persist → AI — using synthetic fixtures. No live Oracle box needed. Run after any proxy or scoring code change to confirm end-to-end behavior.

⚡ Each run creates a real health_check record under `selftest@tunevault.app`. Reports are fully viewable. The critical scenario is the primary regression check — it exercises all 4 new EBS checks from the bug-fix task.
Run a Scenario
HEALTHY
All-green baseline
All CMs running at target, no patching, backups fresh, WF Mailer up. Use to confirm EBS sections render correctly when everything is healthy.
score ≥ 85 EBS OK ADOP: none backup: OK
WARNING
Degraded — amber paths
Tablespace at 86%, OPP below target (2/4 running), WF notification backlog >2h, requests pending elevated. Use to validate amber severity rows and warning-level EBS checks.
score 55–70 OPP: degraded WF backlog TS: 86%
CRITICAL ★ PRIMARY
Full failure — primary regression check
ICM down, OPP down (0/4), WF Mailer + Agent Listener stopped, 2 failed ADOP sessions, tablespaces >98%, 84 invalid objects. Exercises all 4 bug-fix EBS checks.
score < 40 ICM: DOWN OPP: DOWN WF services: STOPPED ADOP: FAILED TS: 98%
EBS PATCHING
ADOP cutover in progress
1 active ADOP session in CUTOVER phase (status R). Most CMs paused, OPP at 1/4. Use to validate ADOP amber state renders correctly and does not show as critical.
score 65–80 ADOP: CUTOVER OPP: 1/4 CM: paused
Recent Runs
Loading…
Regression Guide

### Which scenario to use for each regression class

Scenario | Use when you change… | What to verify
--- | --- | ---
critical | EBS check rows, scoring, Critical Issues rendering, ADOP logic, WF service components | Red badges on EBS_CM01, EBS_CM03, EBS_WF09, EBS_ADOP_SESSIONS. "Critical Issues" header visible. AI summary mentions EBS failures.
warning | Amber severity paths, OPP degraded check, notification backlog thresholds | Amber badges on EBS_CM03 (2/4), EBS_WF08. Score 55–70. No red in Critical Issues.
ebs_patching | ADOP session detection, patching-in-progress UX, active vs failed session distinction | EBS_ADOP_SESSIONS shows amber (not red). Message reads "1 active ADOP… CUTOVER phase". CMs show as degraded, not down.
healthy | Baseline rendering, PDF export, overall score calculation | Score ≥ 85. No Critical Issues. All EBS checks green. PDF export produces complete document with EBS tab.

### curl equivalent

    # Run critical scenario (primary regression check after any EBS code change)
    curl -X POST https://tunevault.app/api/admin/proxy/self-test \
         -H "Authorization: Bearer <YOUR_ADMIN_TOKEN>" \
         -H "Content-Type: application/json" \
         -d '{"scenario":"critical"}'

    # Response includes report URL — open in browser to verify full render
    # {"success":true,"health_check_id":123,"scenario":"critical","overall_score":38,
    #  "ebs_detected":true,"ebs_status":"critical","ai_outcome":"ai","total_ms":8200,
    #  "report_url":"/report/123"}