You can monitor the health of VMware Aria Automation services with the VMware Infrastructure Health.
Resources Monitored for VMware Aria Automation
VMware Infrastructure Health collects the health of the following
VMware Aria 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
Note:
By default, VMware Infrastructure Health monitors all VMware Aria Automation 8.x services. If you do not want certain VMware Aria Automation services to be monitored, you must add the Automation services names (such as endpoints, kube-dns, ebs, etc.) in the VMware Infrastructure Health properties file under the key CAS_SERVICE_TO_IGNORE.
If the VMware Aria Automation is attached to the load balancer, activate port forwarding to monitor Automation services with VMware Infrastructure Health. Refer to Knowledge Base for more details. Ignore these steps if the VMware Aria Automation is a standalone node deployment.
