Missing OTel Details in the Controller UI

If you face any of the following issues occur:
  • The OTel tab does not appear in the Controller UI.
  • The x-api-key is unavailable in the OTel tab.
  • You cannot register your applications in the dashboard.
  • The application data is unavailable in the Controller UI.

Update the admin.jsp page manually or run the following command to update all the required settings. For all the required Controller settings, see Admin.jsp Settings.

Note: This will override the existing admin.jsp settings.

After updating the admin.jsp settings, complete the following steps:

Standard Deployment

  1. Run the following command:

    CODE 
    appdcli run bootstrap_otis

  2. (Optional) Re-configure the required settings on the admin.jsp page. See Admin.jsp Settings.

  3. Re-login to the Controller UI.

Hybrid Deployment

  1. Run the following command:

    CODE 
    appdcli run bootstrap_otis --addAgentConfig=True

  2. (Optional) Re-configure the required settings on the admin.jsp page. See Admin.jsp Settings.

  3. Re-login to the Controller UI.

Admin.jsp Settings

Navigate to the required operation and update its settings:

Enable Service

Standard Deployment
CODE 
appdynamics.onprem.otis.enabled: true
Hybrid Deployment
CODE 
appdynamics.onprem.otis.enabled: true

Onboarding Endpoint

Standard Deployment
CODE 
appdynamics.saas.otis.global.endpoint.url: https://otis-onboarding-service.cisco-otis.svc:18443/Stage/status
Hybrid Deployment
CODE 
appdynamics.saas.otis.global.endpoint.url: https://<virtualappliance-dns-name>/otis/onboarding/Stage/status

API Key to Onboard

Standard Deployment
  1. Run the following command in one of the Virtual Appliance nodes to obtain the x-api-key.
    CODE 
    appdcli key otis_onboarding true

  2. Update the below setting with x-api-key.

    CODE 
    appdynamics.saas.otis.x-api-key: <x-api-key-value>
Hybrid Deployment
  1. Run the following command in one of the Virtual Appliance nodes to obtain the x-api-key.
    CODE 
    appdcli key otis_onboarding true

  2. Update the below setting with x-api-key.

    CODE 
    appdynamics.saas.otis.x-api-key: <x-api-key-value>

Enable Ingestion

Standard Deployment
CODE 
appdynamics.saas.otis.ingestion.endpoint.url: https://<virtual-appliance-dnsname>:443/otis/ingest/
Note: This setting applies only for the internal configuration only. For OTel Collector settings, see the otel-collector.yaml files.
Hybrid Deployment
CODE 
appdynamics.saas.otis.ingestion.endpoint.url: https://<virtual-appliance-dnsname>:443/otis/ingest/

Enable Metering

Standard Deployment
CODE 
appdynamics.saas.otis.usage.global.endpoint.url: https://otis-metering-reader-service.cisco-otis.svc:5001/v1/usage
Hybrid Deployment
CODE 
appdynamics.saas.otis.usage.global.endpoint.url: https://<virtual-appliance-dns-name>/otis/metering/v1/usage

API Key to Enable Metering

Standard Deployment

  1. Run the following command in one of the Virtual Appliance nodes to obtain metering API key:

    CODE 
    appdcli key otis_metering true

  2. Update the below setting with x-api-key:

    CODE 
    appdynamics.saas.otis.usage.x-api-key: <metering-api-key-value>
Hybrid Deployment

  1. Run the following command in one of the Virtual Appliance nodes to obtain metering API key:

    CODE 
    appdcli key otis_metering true

  2. Update the below setting with x-api-key:

    CODE 
    appdynamics.saas.otis.usage.x-api-key: <metering-api-key-value>