You can monitor the following services associated with VMware Aria Automation with the VMware Infrastructure Health.

Note:

By default, VMware Infrastructure Health monitors all VMware Aria Automation 8.x services. In case 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.

Note:

If the VMware Aria Automation is attached to the load balancer, enable 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.

Table 1. 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