Understanding Aria Operations Alerts for Aria Automation 8.x

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 Aria Automation. 

Environment

Aria Operations 8.x 
Aria Automation 8.x

Resolution

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

Alert	Description	Troubleshooting Suggestions
VMware Aria Automation Server Status is Down	Triggered when the VMware Aria Automation server status is down.	Validate the status of the Aria Automation server and services by running the following commands by connecting to the Aria Automation node via SSH with root credentials: vracli status vracli status deploy vracli service status kubectl get pods -n prelude kubectl get nodes vracli disk-mgr df -h (if a clustered set up is in use, validate disk space on all nodes )
VMware Aria Automation Service health is not healthy	Triggered when the VMware Aria Automation service health is not healthy.
VMware Aria Automation Service is in Failed/Down State	Triggered when the VMware Aria Automation service is in the Failed or Down state.
VMware Aria Automation Service health is degraded	Triggered when the VMware Aria Automation health has degraded.
Unable to discover VMware Aria Automation health services	Triggered when the VMware Aria Automation Server (with load balancer) does not have the port forwarding configuration enabled for port 8008.	Review the Load-balancing configuration for the health check port as when the VMware Aria Operations is used you may need to expose the health check port as a virtual server. Refer VMware Aria Automation Load Balancing Guide | Also refer Knowledge Base.
Notifications
Notifications generated when VMware Aria Automation nodes are down	Triggered when the VMware Aria Automation nodes are down and the notification automatically gets cancelled when the nodes are up.

You can monitor the following services associated with VMware Aria Automation with the VMware Infrastructure Health. A few of the services may be seen as stopped on the Aria Automation when reviewing the services using vracli service status, and may not always be due to issues with the services, they also may be flagged stopped as the respective functionalities may not yet be in use, like the idem-xx services and kube-proxy, or may be moved out of the scope of prelude.
Refer : Knowledge Base 314755 and Knowledge Base 336727   

VMware Aria Automation Services

Description

List of Automation services: ingress-ctl kube-dns etcd-service health-reporting-service kube-apiserver kube-controller-manager kube-flannel-ds kube-proxy kube-scheduler kubelet-rubber-stamp predictable-pod-scheduler tiller-deploy openfaas abx-service approval-service assessment-service ui catalog-service cgs-service cmx-service codestream docker-registry ebs form-service hcmp-service identity-service migration-service no-license postgres project-service provisioning-service proxy-service rabbitmq-ha relocation-service tango-blueprint-service tango-vro terraform-service user-profile-service vco adapter-host-service endpoints lemans-resources lemans-gateway private-cloud-gateway