Install Splunk AppDynamics Services in the Standard Deployment

Learn how a standard deployment installs the required infrastructure and services in a Kubernetes cluster.

With the standard deployment option, Splunk AppDynamics On-Premises Virtual Appliance installs infrastructure and Splunk AppDynamics Services in your Kubernetes cluster.

Prepare to Install Splunk AppDynamics Services

Complete the following steps to prepare the environment:

  1. Log in to one of the node console using the appduser credentials.
  2. Navigate to the following folder:
    CODE 
    cd /var/appd/config
  3. Edit the globals.yaml.gotmpl file with the required configuration.
    CODE 
    vi globals.yaml.gotmpl
    1. (Optional) Configure a custom ingress certificate (by default the ingress controller installs a fully-configured self-signed certificate). The custom ingress certificate needs certain SANs added to it. Run the following script on the console of your primary node to view a list of SANs. Add those SANs to your custom ingress certificate. See ingress in Customize the Helm File for instructions on how to configure the custom ingress certificate and key.
      Note: If you are running this script for the first time, copy the code for plain YAML. If you are running this script after installing the services, copy the code for encrypted YAML.
      CODE 
      #!/bin/bash
set -euo pipefail
TENANT=$(grep -v "^ *\t* *{{" /var/appd/config/globals.yaml.gotmpl | yq -r '.appdController.tenantAccountName') DNS_DOMAIN=$(grep -v "^ *\t* *{{" /var/appd/config/globals.yaml.gotmpl | yq -r '.dnsDomain')echo Verify the Virtual Appliance tenant should be \'${TENANT}\'
echo Verify the Virtual Appliance domain name should be \'${DNS_DOMAIN}\'for server_name in "${TENANT}.auth.${DNS_DOMAIN}" "${TENANT}-tnt-authn.${DNS_DOMAIN}"; do
  if ! getent hosts "${server_name}" > /dev/null; then
    echo "Please double-check that DNS can resolve '${server_name}' as the VA ingress IP"
  fi
done

      Sample output of the script above:

      CODE 
      Verify the Virtual Appliance tenant should be 'customer1'
Verify the Virtual Appliance domain name should be 'va.mycompany.com'
Verify the Virtual Appliance node names are: localhost vanodename-1
If creating and importing into VA a Custom Ingress Certificate, include the following SANs:
  va.mycompany.com
  customer1.va.mycompany.com
  *.va.mycompany.com
  customer1.auth.va.mycompany.com
  customer1-tnt-authn.va.mycompany.com
  localhost
  vanodename-1
    2. (Optional) Add any custom CA certificates for Controller outbound traffic by configuring appdController.customCaCerts in Customize the Helm File.
    3. (Optional) Disable the self-monitoring for the Controller.
      CODE 
      enableClusterAgent: false
  4. (Optional) Edit the /var/appd/config/secrets.yaml file to update usernames and passwords of the Splunk AppDynamics Services.
    CODE 
    vi /var/appd/config/secrets.yaml
    Note: When you install the Splunk AppDynamics service, the secrets.yaml file becomes encrypted.
    See Edit the secrets.yaml.encrypted file.
  5. Save the following script to the console of your primary virtual appliance node as dnsinfo.sh and run it. Follow the instructions in its output:
    CODE 
    #!/bin/bash
set -euo pipefail
TENANT=$(grep -v "^ *\t* *{{" /var/appd/config/globals.yaml.gotmpl | yq -r '.appdController.tenantAccountName') DNS_DOMAIN=$(grep -v "^ *\t* *{{" /var/appd/config/globals.yaml.gotmpl | yq -r '.dnsDomain')echo Verify the Virtual Appliance tenant should be \'${TENANT}\'
echo Verify the Virtual Appliance domain name should be \'${DNS_DOMAIN}\'for server_name in "${TENANT}.auth.${DNS_DOMAIN}" "${TENANT}-tnt-authn.${DNS_DOMAIN}"; do
  if ! getent hosts "${server_name}" > /dev/null; then
    echo "Please double-check that DNS can resolve '${server_name}' as the VA ingress IP"
  fi
done

    Sample output:

    CODE 
    Verify the Virtual Appliance tenant should be 'customer1'
Verify the Virtual Appliance domain name should be 'va.mycompany.com'
Please double-check that DNS can resolve 'customer1.auth.va.mycompany.com' as the VA ingress IP
Please double-check that DNS can resolve 'customer1-tnt-authn.va.mycompany.com' as the VA ingress IP
  6. Copy the license files as the license.lic file to the node in the following location.
    CODE 
    cd /var/appd/config
    This license will be automatically used to provision Splunk AppDynamics Services. If you do not have the license file at this time, you can apply the license and provision the services later using appdcli.
    Note: For End User Monitoring, if you are using the Infrastructure-based Licensing model, make sure to specify EUM account and license key in the Administration Console. See Access the Administration Console.

Create a Three-Node Cluster

  1. Log in to the primary node console.
  2. Verify the boot status of each node of the cluster:
    CODE 
    appdctl show boot
    Note:
  3. Run the following command in the primary node and specify the IP address of the peer nodes:
    CODE 
    cd /home/appduser
appdctl cluster init <Node-2-IP> <Node-3-IP>
  4. Run the following command to verify the node status:
    CODE 
    appdctl show cluster
microk8s status

    Ensure that the output displays the Running status as true for the nodes that are part of the cluster.

    Sample Output

    CODE 
    NODE           | ROLE  | RUNNING 
----------------+-------+---------
 10.0.0.1:19001 | voter | true    
 10.0.0.2:19001 | voter | true    
 10.0.0.3:19001 | voter | true
    Note: You must re-login to the terminal if the following error is displayed:
    CODE 
    Insufficient Permissions to Access Microk8s

Install Services in the Cluster

Install AppDynamics Services in a standard deployment by running the appdcli command for the selected profile.

  1. Log in to the cluster node console.
  2. Run the command to install services:
    CODE 
    appdcli start appd [Profile]
    Small Profile
    CODE 
    appdcli start appd small
    Medium Profile
    CODE 
    appdcli start appd medium
    Large Profile
    CODE 
    appdcli start appd large
    Extra Large Profile
    CODE 
    appdcli start appd xlarge

    This command installs the Splunk AppDynamics services. We recommend that you specify the same VA profile that you selected to create a virtual machine. See, Sizing Requirements.

    Sample Output

    CODE 
    NAME               CHART                     VERSION   DURATION
cert-manager-ext   charts/cert-manager-ext   0.0.1           0s
ingress-nginx      charts/ingress-nginx      4.8.3           1s
redis-ext          charts/redis-ext          0.0.1           1s
ingress            charts/ingress            0.0.1           2s
cluster            charts/cluster            0.0.1           2s
reflector          charts/reflector          7.1.216         2s
monitoring-ext     charts/monitoring-ext     0.0.1           2s
minio-ext          charts/minio-ext          0.0.1           2s
eum                charts/eum                0.0.1           2s
fluent-bit         charts/fluent-bit         0.39.0          2s
postgres           charts/postgres           0.0.1           2s
mysql              charts/mysql              0.0.1           3s
redis              charts/redis              18.1.6          3s
controller         charts/controller         0.0.1           3s
events             charts/events             0.0.1           4s
cluster-agent      charts/cluster-agent      1.16.37         4s
kafka              charts/kafka              0.0.1           6s
minio              charts/minio              5.0.14         47s
  3. Verify the status of the installed pods and service endpoints:
    • Pods: kubectl get pods --all-namespaces

    • Service endpoints: appdcli ping

      CODE 
      +---------------------+---------+
|  Service Endpoint   | Status  |
+=====================+=========+
| Controller          | Success |
+---------------------+---------+
| Events              | Success |
+---------------------+---------+
| EUM Collector       | Success |
+---------------------+---------+
| EUM Aggregator      | Success |
+---------------------+---------+
| EUM Screenshot      | Success |
+---------------------+---------+
| Synthetic Shepherd  | Success |
+---------------------+---------+
| Synthetic Scheduler | Success |
+---------------------+---------+
| Synthetic Feeder    | Success |
+---------------------+---------+
| AD/RCA Services     | Failed  |
+---------------------+---------+
Note:

By default, Virtual Appliance installs the Cluster Agent. This agent helps you monitor nodes, CPU, memory and storage. For more information, see View Container Details.

Install the Anomaly Detection Services in the Cluster

Install Anomaly Detection services in the cluster by running the profile-specific appdcli command.

  1. Log in to the cluster node console.
  2. Run the command to install services:
    Small Profile
    CODE 
    appdcli start aiops small
    Medium Profile
    CODE 
    appdcli start aiops medium
    Large Profile
    CODE 
    appdcli start aiops large
    Extra Large Profile
    CODE 
    appdcli start aiops xlarge
  3. Verify the status of the installed pods and service endpoints:
    • Pods: kubectl get pods -n cisco-aiops

    • Service endpoints: appdcli ping

      The status of the Anomaly Detection service appears as Success.

See Anomaly Detection.
Note: Sometimes, IOException error occurs when you access Anomaly Detection in the Controller UI. See Troubleshoot Virtual Appliance Issues.

Install OpenTelemetry Service

Install the OpenTelemetry service in an On-Premises Virtual Appliance hybrid deployment.

Ensure the following conditions are met:

  • OpenTelemetry Collector version 0.36 to 0.101.
  • The maximum size limit for each request sent to the trace ingestion endpoint is 10 MB.
  1. Go to the Controller DNS to verify that the Controller is active.
  2. Log in to the cluster node console.
  3. Run the following command and wait until the Controller service status is Success.
    CODE 
    appdcli ping
    Sample Output:
    CODE 
    +---------------------+---------------+
|  Service Endpoint   |    Status     |
+=====================+===============+
| Controller          | Success       |
+---------------------+---------------+
| Events              | Success       |
+---------------------+---------------+
| EUM Collector       | Success       |
+---------------------+---------------+
| EUM Aggregator      | Success       |
+---------------------+---------------+
| EUM Screenshot      | Success       |
+---------------------+---------------+
| Synthetic Shepherd  | Success       |
+---------------------+---------------+
| Synthetic Scheduler | Success       |
+---------------------+---------------+
| Synthetic Feeder    | Success       |
+---------------------+---------------+
| OTIS                | Not Installed |
+---------------------+---------------+
  4. Run the following command to install the OpenTelemetry™ service:
    Small Profile
    CODE 
    appdcli start otis small
    Medium Profile
    CODE 
    appdcli start otis medium
    Large Profile
    CODE 
    appdcli start otis large
    Extra Large Profile
    CODE 
    appdcli start otis xlarge

    This command installs the OpenTelemetry™ service in the cisco-otis namespace.

  5. Verify the status of the installed pods and service endpoints:
    • Pods: kubectl get pods -n cisco-otis

    • Service endpoints: appdcli ping

      The status of the OpenTelemetry™ service appears as Success.
      CODE 
      +---------------------+---------------+
|  Service Endpoint   |    Status     |
+=====================+===============+
| Controller          | Success       |
+---------------------+---------------+
| Events              | Success       |
+---------------------+---------------+
| EUM Collector       | Success       |
+---------------------+---------------+
| EUM Aggregator      | Success       |
+---------------------+---------------+
| EUM Screenshot      | Success       |
+---------------------+---------------+
| Synthetic Shepherd  | Success       |
+---------------------+---------------+
| Synthetic Scheduler | Success       |
+---------------------+---------------+
| Synthetic Feeder    | Success       |
+---------------------+---------------+
| OTIS                | Success       |
+---------------------+---------------+

    You can also access the endpoint URL to verify the installation. See Verify the Service Endpoints Paths.

Configure AppDynamics for OpenTelemetry.

Install ATD Services

Prepare and install Automated Transaction Diagnostics services in the cluster.

Ensure that the AuthN service is installed along with Splunk AppDynamics services.
CODE 
kubectl get pods -nauthn

Follow the steps to install Automatic Transaction Diagnostics service in the Virtual Appliance:

  1. Log in to the cluster node console.
  2. Run the command to install services:
    Demo Profile
    CODE 
    appdcli start atd demo
    Small Profile
    CODE 
    appdcli start atd small
    Medium Profile
    CODE 
    appdcli start atd medium
    Large Profile
    CODE 
    appdcli start atd large
    Extra Large Profile
    CODE 
    appdcli start atd xlarge
  3. Verify the status of installed pods and service endpoints.
    CODE 
    kubectl get pods -ncisco-atd

    You can also access the endpoint URL to verify the installation. See Verify the Service Endpoints Paths.

    For more information about ATD, see Automated Transaction Diagnostics Workflow.

Log in to administrator console (admin.jsp) and update the following properties in Controller Settings.
CODE 
metrics.min.retention.period = 20
atd.onprem.enabled = true

Install Universal Integration Layer Service

Install the Universal Integration Layer service in the Virtual Appliance cluster.

To integrate Splunk AppDynamics Self Hosted Virtual Appliance with Splunk Enterprise, you must install the Universal Integration Layer (UIL) service in the cluster:
  1. Log in to the cluster node console.
  2. Run the command to install the service:
    Small Profile
    CODE 
    appdcli start uil small
    Medium Profile
    CODE 
    appdcli start uil medium
    Large Profile
    CODE 
    appdcli start uil large
    Extra Large Profile
    CODE 
    appdcli start uil xlarge
  3. Verify the status of the installed pods and service endpoints:
    • Pods: kubectl get pods -n cisco-uil

      The status of the universal integration layer pod must be displayed as Running.

      UIL Pods

    • Service endpoints: appdcli ping

      The status of the UIL service should be displayed as Success.

      UIL Service Endpoints

    You can also access the endpoint URL to verify the installation. See Verify the Service Endpoints Paths.

To continue with the integration, see Integrate Splunk AppDynamics Self Hosted Virtual Appliance with Splunk Enterprise.

Apply Licenses to Splunk AppDynamics Services

Use appdcli to apply licenses after installing Splunk AppDynamics Services.

  1. Log in to the cluster node console.
  2. Copy the license files as the license.lic file to the node in the following location.
    CODE 
    cd /var/appd/config
  3. Run the following commands to apply licenses:
    Controller

    Update the Controller license.

    CODE 
    appdcli license controller license.lic
    End User Monitoring
    1. Update the EUM license.
      CODE 
      appdcli license eum license.lic
    2. (Optional) If you are using the Infrastructure-based Licensing model, make sure to specify EUM account and license key in the Administration Console. See Access the Administration Console. Follow the steps to add EUM account and license key:

      1. From Account Settings, select the Controller account that have EUM licenses and click Edit.

      2. Enter the EUM license key and the EUM account name in the EUM License Key and the EUM Account Name fields.

      3. Click Save.

    For more information, see Virtual Appliance CLI.

Verify the Service Endpoints Paths

Review service endpoint paths for Controller, Events, EUM, and related Virtual Appliance services.

Log in to the Controller UI by accessing https://<DNS-Name>or<Cluster-Node-IP>/.

The Ingress controller checks the URL of an incoming request and redirects to the respective Splunk AppDynamics Service.

Service Endpoint Installation Path
Controller https://<ingress>/controller
Events

https://<ingress>/events

https://<Node-IP>:32105/events
End User Monitoring Aggregator https://<ingress>/eumaggregator
Screenshots https://<ingress>/screenshots
Collector https://<ingress>/eumcollector
Synthetic Shepherd https://<ingress>/synthetic/shepherd
Scheduler https://<ingress>/synthetic/scheduler
Feeder https://<ingress>/synthetic/feeder
Note: By default, the Controller UI username is set to admin and the password is set to welcome.