Home
AVX Setup
Get detailed instructions for setting up AVX ONE in on-premises or SaaS deployments.
AppViewX On-Prem Setup Guides
Install, Upgrade, and Maintenance Guide
Auto Remediation Configuration
Auto Remediation is installed as part of the AppViewX application installation. After installation, administrators and Support Engineers configure and operate the monitoring platform from the AppViewX Interactive IU. A separate standalone Auto Remediation installer is not the primary customer configuration path.
Troubleshooting
Primary logs: logs/auto_remediation_*.log and Interactive IU logs. Do not attach secrets.

CLM
Automate certificate lifecycle management including issuance, discovery, renewal, and deployment, across public and private trust CAs. Assess, prioritize, and plan your migration to quantum-safe encryption with the Quantum Trust Hub add-on module.
PKI
Provision, govern and scale private trust certificates with a Post Quantum ready cloud based Enterprise PKI-as-a-Service.
Code Signing
Secure software, firmware, and containers with a comprehensive enterprise code signing solution.
SSH
Control SSH access and key rotation at scale with an SSH key lifecycle management solution.
KUBE
Unify DevOps and Security teams by managing certificates with a Kubernetes-native certificate lifecycle management solution.
DDI
Manage domain registration, renewal, decommissioning, and other security controls with an end-to-end domain lifecycle management solution.
ADC
Automate and orchestrate application delivery infrastructure at scale with an ADC lifecycle automation platform.
Platform
Manage policy and automation across all of the products and modules in the AVX ONE platform.
AVX Setup
Get detailed instructions for setting up AVX ONE in on-premises or SaaS deployments.
- AppViewX On-Prem Setup Guides
  - Install, Upgrade, and Maintenance Guide
    - Platform Overview
    - System Requirements and Prerequisites
    - AppViewX Installation
      All AppViewX installation is performed through the Interactive UI a full-screen terminal wizard launched by running ./install.sh. There is no separate manual CLI installation path. The wizard collects all configuration, validates prerequisites on all target nodes, and deploys the platform automatically.
    - Upgrade AppViewX
    - AppViewX Patch Management
    - Auto Remediation Configuration
      Auto Remediation is installed as part of the AppViewX application installation. After installation, administrators and Support Engineers configure and operate the monitoring platform from the AppViewX Interactive IU. A separate standalone Auto Remediation installer is not the primary customer configuration path.
      - 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.
      - Prerequisites
        This topic describes Prerequisites.
      - Accessing Auto Remediation Configuration
        This topic describes Accessing Auto Remediation Configuration.
      - Auto Remediation Configuration Menu
        The submenu is displayed exactly as follows:
      - Configuration Reference
        Parameters below are taken from scripts/auto_remediation.conf-template.template, the Interactive IU conf editor, and auto_remediation.sh validation. Do not add parameters that are not present in those sources. Site-specific live values are not documented here.
      - Validation
        Use this checklist after configuration changes.
      - Troubleshooting
        Primary logs: logs/auto_remediation_*.log and Interactive IU logs. Do not attach secrets.
    - MongoSync Setup and Operations
      This guide provides setup, configuration, initial sync, operations, monitoring, and troubleshooting guidance for AppViewX MongoSync based DR replication.
    - AppViewX Utility Reference
    - Installing ELK Components
    - Enabling the Insight Module
    - Platform Administration and Operations
    - External Certificate for Kubernetes
    - Dynamic API's Addition Script
    - Kubernetes Architecture and Deployment Model
    - Disaster Recovery Plan
    - Troubleshooting
    - Appendix A: appviewx.conf Reference
    - Appendix B: Security Placeholder Reference
    - Appendix C: Glossary
    - Whitelisting UI Access Hosts (On-Premise Deployments)
      AppViewX Web UI is typically accessed via Istio ingress (NodePort) and/or a Load Balancer URL. This topic explains how to whitelist the hostnames/IPs (URLs) that are allowed to access the AppViewX Web UI in on-premise deployments.
    - Uninstalling AppViewX
    - Troubleshooting
    - Disable Kex Algorithm Guide
    - Migrating CentOS to Ubuntu/RHEL
    - Upgrading RHEL to v8.10/v9.4
    - Upgrading Ubuntu 20.04 to Ubuntu 22.04
    - Upgrading Ubuntu 22.04 to Ubuntu 24.04
    - OS Patching on Ubuntu for Multi-Node Environment
- AppViewX SaaS Setup Guides
- Managed Kubernetes
- OpenShift Deployment with ArgoCD
- MSP Portal User Guide
- AppViewX Windows Gateway Setup
- AppViewX on ServiceNow Guides
- AppViewX Supported Integrations
- Support
- Glossary
Artifacts
Review new features, fixes, and security advisories with official AppViewX release documentation.

Troubleshooting

Primary logs: logs/auto_remediation_*.log and Interactive IU logs. Do not attach secrets.

Configuration validation failure


Item	Detail
Symptoms	IU or script reports invalid YAML, missing node_manager or cluster_manager, empty required conf keys, or auto_remediation.conf appears incomplete.
Possible cause	Edit errors, truncated copy, template not instantiated, or the wrong file was edited.
Resolution	Restore structure from auto_remediation_config-template.yaml.template or auto_remediation.conf-template.template. Re-run option 4, then option 5 or 1.
Validation	Option 4 reports YAML validated. Reload or apply validation passes.

Apply Configuration failure


Item	Detail
Symptoms	IU reports Apply Configuration failed with a non-zero exit. Script errors on ConfigMap, SSH, or systemd.
Possible cause	Operator missing, Node Manager missing, SSH or sudo failure, or apply error after a real YAML change.
Resolution	Fix prerequisites. Check logs/auto_remediation_*.log. Retry option 5. For Node Manager, confirm systemctl status appviewx-node-manager.service.
Validation	Skip message if unchanged, or success for type. Pods Ready.

Reload Configuration failure


Item	Detail
Symptoms	Reload Configuration failed, abort because RQLite nodes changed, or rollback message.
Possible cause	Invalid conf, Helm timeout, sudo missing for Node Manager, or RQLite topology edited in conf.
Resolution	If RQLite nodes changed, reinstall or redeploy instead of reload. Otherwise fix conf, review backup under logs/auto_remediation_config_backup_*, retry option 1.
Validation	[INFO] skip if unchanged, or [SUCCESS] reload. kubectl get pods -n auto-remediation.

SMTP synchronization failure


Item	Detail
Symptoms	Product SMTP missing or incomplete, sync exit non-zero, or SMTP still incomplete after sync.
Possible cause	AppViewX UI SMTP not set, application database unreachable, manual source blocking overwrite, or operator missing.
Resolution	Configure Settings -> General -> SMTP. Retry option 2. Do not paste passwords. If manual SMTP is intended, complete it via option 1 conf edit rather than forcing product overwrite.
Validation	Masked preview shows server, from, and to. smtp-credentials exists. Option 6 is no longer blocked on SMTP.

Alert Cycle failure


Item	Detail
Symptoms	Cannot run Alert Cycle; SMTP errors; ALERT_MANUAL_TRIGGER_ENABLED; operator not ready; already in progress.
Possible cause	Prerequisites listed in section 5.6 are not met, or a concurrent job is running.
Resolution	Complete options 5 and 2. Set ALERT_MANUAL_TRIGGER_ENABLED=true if it is false, then reload. Inspect jobs and logs in namespace auto-remediation.
Validation	Alert cycle completed, or a clear no-waiting-alerts or already-in-progress message.

Report generation failure


Item	Detail
Symptoms	Cannot generate report; generator missing; RQLite not reachable; directory not writable.
Possible cause	RQLite not installed, rqlite-auth missing, Python missing, or disk permissions.
Resolution	See section 5.7. Repair the RQLite Helm release. Fix REPORT_OUTPUT_DIR permissions.
Validation	HTML file or CSV directory created. IU success line.

RQLite connectivity issues


Item	Detail
Symptoms	Reports fail, operator cannot persist findings, or secret rqlite-auth is missing.
Possible cause	StatefulSet not Ready, service rqlite down, auth secret lost, or network policy.
Resolution	kubectl get sts,pods,svc -n auto-remediation. Check Helm release rqlite. Restore from install if required.
Validation	rqlite pods Ready. Report option 7 succeeds.

Missing Kubernetes resources


Item	Detail
Symptoms	IU prerequisite errors for namespace, operator, ConfigMaps, secrets, or rqlite.
Possible cause	Failed or incomplete AppViewX installation, or a partial uninstall of Auto Remediation.
Resolution	Re-run Auto Remediation install from scripts: ./auto_remediation.sh --install --non-interactive. Do not invent resource names.
Validation	Resources listed in section 3 are present.

Auto-Fix/Remediation Failures


Item	Detail
Symptoms	Issues persist in reports or alerts. Pods remain unhealthy. Node Manager checks fail.
Possible cause	Plugin autofix is false (including kube_certs by default), check not enabled, insufficient sudo, or unsafe autofix skipped.
Resolution	Inspect auto_remediation_config.yaml autofix flags. Do not enable kube_certs autofix unless downtime is accepted. Fix underlying infrastructure, re-apply YAML, and review operator and node-manager logs.
Validation	Option 3 export shows intended autofix flags. Subsequent report or alert reflects the new state.

AppViewX