Follow these steps to configure monitoring for Tanzu Mission Control.

Procedure

  1. From the left menu, click Data Sources > Integrations, and then click Repository in the right pane.
  2. Click Add Account on the VMware Aria Operations Management Pack for Kubernetes tile.
    Note: Alternatively, you can navigate to Data Sources > Integrations, and then click the Accounts tab. Click Add Accounts to configure the adapter instance.
  3. Select Tanzu Mission Control from the adapter list and configure the adapter instance.

    Field Name

    Action

    Name

    Enter the name for this instance of the TMC adapter as you want it to appear in VMware Aria Operations.

    Description

    Enter the description for the instance with any additional information that helps you manage your instances.

    TMC URL

    Enter the URL for the TMC cloud instance that the TMC adapter needs to connect to discover the clusters.
  4. Select the credential you want to use to sign on to the environment from the drop-down menu. To add new credentials, click the + icon.

    Field Name

    Action

    Credential Name

    Enter the name by which you can identify the configured credentials.

    This will be stored in the Credential section in Integrations.
    CSP Refresh Token Enter the CSP token required for authentication in the TMC environment.

    Enter the details of the proxy server to which VMware Aria Operations must connect to only if a proxy server is used to connect to TMC
    Proxy Hostname Enter the hostname of the proxy server to which VMware Aria Operations needs to connect.
    Proxy Port Enter the port of the proxy server.
    Proxy Username Enter the username to authenticate while connecting to the proxy server.
    Proxy Password Enter the password to authenticate while connecting to the proxy server.

    Prometheus endpoint token (Only for the Red Hat OpenShift clusters)
    Note: This is relevant only for clusters discovered by the Red Hat OpenShift adapter.
    Enter the bearer token to authenticate the Prometheus server.
  5. Select the collector or collector group on which you want to run the adapter instance from the Collector/Groups drop-down. This option is set to the optimal collector by default.
  6. Click Validate Connection to check if you can successfully connect to the TMC endpoint.
  7. Optionally, use Advanced Settings to define the following:

    Field Name

    Action

    Auto-accept Kubernetes Cluster SSL Certificate
    Use this field to decide if you want to automatically accept untrusted certificates presented by the discovered Kubernetes clusters.

    • Select the Enabled option to automatically accept the untrusted certificates presented by the discovered clusters. This option is selected by default.

    • Select the Deactivated option to manually accept the untrusted certificates for the discovered Kubernetes clusters.
    Enable cAdvisor Install Check Use field is to perform a check on the discovered Kubernetes cluster to see if cAdvisor has been installed.

    Select the Enabled option to check whether cAdvisor has been installed in the cluster.

    Select the Deactivated option to deactivate install check on cAdvisor. This option is selected by default.

    Auto-delete Kubernetes Adapter Instance

    Use this field to automatically delete the Kubernetes adapter instance created for a discovered cluster if the cluster has been deleted in TMC as well.

    Select the Enabled option to automatically delete the Kubernetes adapter instances for clusters that have been deleted in the Kubernetes environment via TMC.

    Select the Deactivated option to retain the Kubernetes adapter instances even if they are deleted in the Kubernetes environment by TMC. These adapter instances will have to be deleted manually. This option is selected by default.
  8. Click Add.