Understanding Aria Operations Alerts for VMware Identity Manager
search cancel

Understanding Aria Operations Alerts for VMware Identity Manager

book

Article ID: 395392

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This Article aims to provide insights on the various library alerts observed in the Aria Operations when using the Aria Operations Management Pack for VMware Identity Manager. 

Environment

Aria Operations 8.x
VMware Identity Manager 3.x

Resolution

Stated below are the Alerts, descriptions and possible troubleshooting suggestions:   

Alert Description Potential Troubleshooting
Health of vIDM Instance is degraded.  Triggered when the vIDM VM is down. Validating Workspace One Access 3.3.x (formerly VMware Identity Manager) health
Health of ACSHealth-ApplicationDeployment is Low. Triggered when the vIDM ACSHealth-ApplicationDeployment service is down. ACS Health - Application Deployment Status, has failure in the vIDM Health tab causing various errors at vIDM and Aria Automation layer
Health of Application Deployment is Critically Low. Triggered when the Application Deployment service is down.
Health of Application Manager-Application Deployment is Critically Low.
Analytics Connection Test Connection failed. Triggered when the Analytics service is down. vIDM 3.3.x Upgrade Stuck at "Waiting for SaaS to Come Up" or Certificate Replacement Fails Due to Liquibase Lock Error "LCMVIDM73101"

After upgrading to vIDM 3.3.7, user dashboard reporting and Active Directory sync log are not updating: the cluster currently has the maximum number of shards open
Database Test connection failed. Triggered when the Database service is down. Troubleshooting VMware Identity Manager postgres cluster deployed through vRealize Suite Lifecycle Manager
Health of Disk Space is Critically Low. Triggered when the Disk Space on vIDM VM is low. How to Increase vIDM appliance disk space

vIDM appliance has no space left on device /db for audit data

vIDM root partition is full on one node of the cluster
Messaging Server Test Connection failed. Triggered when the Messaging Server service is down RabbitMQ service not starting and showing red in vIDM dashboard
Health of RabbitMQ Service is Critically Low. Triggered when the RabbitMQ service is down.
Health of vIDM AirWatch API Server is Critically low. Triggered when the Manager-Application service is down. Validate service status using:
/usr/local/horizon/scripts/service-control.sh status

Validate log captures from
/opt/vmware/horizon/workspace/logs/catalina.out
/opt/vmware/horizon/workspace/logs/manager.log
Health of vIDM Certificate is not good , look like it is Expired. Triggered when vIDM Certificate has expired or deleted. Certificate Replacement for VMware Identity Manager deployed from Aria Suite Lifecycle
Health of Port Connectivity is Critically Low. Triggered when the Port Connectivity service is down. System and Network Configuration Requirements
Health of FQDN vIDM Server is critically low. Triggered when the FQDN service is down. Identity Manager FQDN health reports error connecting to the identity manager fqdn
Health of Configurator-ApplicationDeployment is Low. Triggered when the Configurator-ApplicationDeployment service is down. vIDM 3.3.x https://<vIDM-FQDN>:8443/cfg/ configurator page throws "Blank red box error"

Stop the horizon workspace service on the affected node using the command: 
service horizon-workspace stop
Update the file /usr/local/horizon/conf/system-config.properties of the affected node with the system-config.properties from the working node or with the referred exampled in Additional Information
Restart the horizon service on the affected node using the command:
service horizon-workspace restart

Health of Elasticsearch / opensearch is Yellow. Triggered when the Elasticsearch service is down. VMware Identity Manager (vIDM / WSA) opensearch service will not start.
Health of Connector-ApplicationDeployment is Critically Low. Triggered when the Connector-ApplicationDeploymen service is down. Validate logs in /opt/vmware/horizon/workspace/logs/connector.log
Validate logs in /opt/vmware/horizon/workspace/logs/horizon.log
Validate configurations in config-state.json file on the affected node