This page describes how to install the Cisco AppDynamics Collectors using the AppDynamics OpenShift OperatorHub Bundle.

AppDynamics OpenShift OperatorHub Bundle is available at RedHat catalog.

Requirements

Before you begin, verify that you have:

Installation Procedure

  1. From the Cisco Cloud Observability Tenant UI, navigate to Configure > Kubernetes and App Services. Enter your Credential set name and Kubernetes cluster name.
  2. Select the required collectors under Enable Additional Configurations to generate the collector values file.
  3. Click Generate configuration file. 
    You must download the generated file to get inline documentation for all the collector settings in the configuration file in the form of comments. So, you can uncomment the parameters that you require without having to search for those in the documentation.
    These downloaded configuration files, collectors-values.yaml and operator-values.yaml will be used further during installation.

  4. Create the Cisco AppDynamics namespace where the Kubernetes and App Service Monitoring Solution is installed:

    kubectl create namespace appdynamics
    CODE


  5. For Kubernetes, the webhook requires a TLS certificate for the API server to communicate with the webhook component of OpenTelemetry Operator in the Splunk AppDynamics Operators Helm chart. The API server must then be configured for the OpenTelemetry Operator. The simplest option is to install cert-manager and allow it to generate a self-signed certificate automatically:

    kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.8.0/cert-manager.yaml
    BASH

    To manually generate a certificate see Provision a TLS Certificate for the OpenTelemetry Operator.

  6. Add the Helm repository

    helm repo add appdynamics-cloud-helmcharts https://appdynamics.jfrog.io/artifactory/appdynamics-cloud-helmcharts/ 
    CODE

  7. Install the AppDynamics Operator:

    1. Go to your OpenShift cluster console

    2. Go to Operators > Appdynamics Cloud Operator 

    3. Search with the appdynamics filter

    4. Click Install

  8. Update the following value in the operators-values.yaml file that you generated in step 3.

    appdynamics-cloud-operator:
  enabled: false
    CODE

  9. Install OpenTelemetry Operator 

     helm install appdynamics-operators appdynamics-cloud-helmcharts/appdynamics-operators -n appdynamics -f operators-values.yaml --wait
    CODE

  10. Install the Splunk AppDynamics Collectors using collectors-values.yaml.

    • To configure mTLS between Splunk AppDynamics Collectors and OpenTelemetry Collectors, see Configure mTLS.

    • To monitor the tainted nodes (if any node in the cluster is tainted), see Monitor the Tainted Nodes.
      In OpenShift clusters, the master nodes are tainted. Therefore, you must configure tolerations on the pods.

    • To configure proxy settings for the Cisco AppDynamics Distribution of OpenTelemetry Collector, see Configure Proxy Settings.

      helm install appdynamics-collectors appdynamics-cloud-helmcharts/appdynamics-collectors -n appdynamics -f collectors-values.yaml
      CODE
  11. Validate the installation:

    Check K8s pods in appdynamics namespace using the following command: 

    kubectl get all -n appdynamics
    BASH

Next Steps

Application Performance Monitoring

Choose the appropriate workflow from Application Performance Monitoring based on your environment. 

Log Collection

Log Collection is inactive by default. Use the Log Ingestion instructions if you require them.

Event Monitoring 

You can observe the event severity for the entities with the details on Cisco Cloud Observability UI. See Kubernetes Events Collection.

Advanced Install and Configuration

Refer to the following pages for advanced settings for Helm charts and APM auto-instrumentation:

Upgrade or Uninstall Kubernetes Full-Stack Monitoring

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.