(Optional) Update the License File

Update or replace the Splunk AppDynamics license file after the initial Kubernetes deployment.

Complete the following tasks after installing Splunk AppDynamics charts in your Kubernetes cluster if any of the following conditions apply:
  • Missing License: A valid license file was not present in the config/ folder before running the install.sh command.
  • License Maintenance: You need to upgrade, change, or renew your license after the initial installation.
Optional: Specify the license path in the command and run it:
Note:

Go to the directory where you have extracted the deployment files.

CODE 
./scripts/update-license.sh <path-to-license.lic>
Example:
CODE 
# Update with default path
./scripts/update-license.sh

# Update with custom path
./scripts/update-license.sh /path/to/new/license.lic
Note: If you do not specify a path, the script uses config/license.lic
The following namespaces are updated:
  • cisco-secureapp
  • cisco-aiops
  • cisco-otis
  • cisco-uil
  • cisco-atd
  • authn

Configure Cisco Secure Applications

Configure Cisco Secure Applications settings, feed keys, and feed data after deploying Splunk AppDynamics services.

Ensure the following conditions are met:
  • The feed key file and feed data file exists.
  • The deployment is active.
For Cisco Secure Application, you require the following configuration in the Controller:
  1. Log in to the administration console (admin.jsp).
    1. Set argento.enabled to true for the tenant
    2. Create a role with appropriate Secure Application permissions and associate with the users who require the SecureApp access.
Set Up Feed Key and Data
  1. Optional: Configure the Cisco Secure Application's feed key and data feed.
    1. Set the feed key.
      CODE 
      # From file
./secapp-charts/secureapp-byok.sh setFeedKey /path/to/feed_key.txt
    2. Upload the feed data file.
      CODE 
      ./secapp-charts/secureapp-byok.sh uploadFeed /path/to/feed-data.dat

Configure ATD Services

Configure Automated Transaction Diagnostics services and verify that the required ATD pods are running in your Kubernetes cluster.

Configure the ATD services to use a custom Kubernetes cluster:
  1. Optional: Verify whether the ATD pods are active.
    CODE 
    kubectl get pods -n cisco-atd -o wide
    Note: Ensure that the ds-sa-svc and snapshot-analyze pods are in active state.
  2. Optional: Check the ATD logs.
    CODE 
    # ds-sa-svc logs
kubectl logs -n cisco-atd -l app=ds-sa-svc --tail=50

# snapshot-analyze logs
kubectl logs -n cisco-atd -l app=snapshot-analyze --tail=50
Update Controller Settings
  1. Log in to the administration console (admin.jsp).
    1. Go to Controller Settings and select the Controller Configurations tab.
    2. Set atd.onprem.enabled to true.
    3. Set metrics.min.retention.period to 40.