Overview

Auto Remediation is installed by default as part of the AppViewX application installation. The installer deploys Auto Remediation into Kubernetes, including the Node Manager host service on worker nodes. After installation, use Interactive IU option 8 to manage configuration without reinstalling AppViewX.

What you configure from the IU

  • Runtime flags in scripts/auto_remediation.conf (SMTP, alerting, schedules, node placement, report output).
  • Check definitions in scripts/auto_remediation_config.yaml (Node Manager and Cluster Manager plugins).
  • Live cluster resources in namespace auto-remediation (operator, cluster-manager, RQLite, SMTP secret, alert CronJob).

Navigation

AppViewX Interactive IU
    |
    ├── 5. Cluster Health Validations     (separate workflow; not this section)
    └── 8. Auto Remediation configuration
            |
            └── Auto Remediation Configuration Menu

Recommended configuration workflow

Prepare / Edit auto_remediation_config.yaml     (option 4)
        ↓
Validate YAML (automatic after edit)
        ↓
Apply Configuration                             (option 5)
        ↓
Use SMTP from AppViewX Product Settings         (option 2)
        ↓
Reload Configuration (if auto_remediation.conf changed)  (option 1)
        ↓
View Configuration                               (option 3)
        ↓
Run Alert Cycle / Generate Report                (options 6 / 7)
Note: Reload Configuration and Apply Configuration skip unnecessary redeployment when no configuration changes are detected. A skip message means no reload or apply ran. It is not a failure, and it is not a successful reload or apply.