You should see a message similar to this for missing server visibility license: [WARNING]: 2020-06-04 15:23:28 - agentregistrationmodule.go:206 - Agent is not licensed ... View more

Two thoughts: generally that error indicates an error with access key, so worth double checking the value. Also have you setup the secret based on that value using: kubectl -n appdynamics create secret generic cluster-agent-secret --from-literal=controller-key=<access-key> as described on this page: https://docs.appdynamics.com/display/PRO45/Deploy+the+Cluster+Agent+on+Kubernetes And finally, do you have an available server visibility license?   ... View more

@Chris.Edwards you would want to configure a cert for the endpoint where the cluster agent ssl connection would terminate, typically with the load balancer. I don't think you'd need the on prem controller cert unless the load balancer to controller connection is using ssl as well. ... View more

Hi @T.Singh  I was tracking down how we can change trial licenses to include a Server Visibility license, which may a few days to sort out. thanks Jeff --- Edited  6/16/20 C. Landivar ... View more

Hi @T.Singh The current docs assume you start with the instructions on https://docs.appdynamics.com/display/PRO45/Install+the+Cluster+Agent and download the cluster agent bundle, which will include the cluster-agent-operator.yaml. However, I can understand how you'd easily start on the 'Deploy the AppDynamics Operator on Kubernetes' page, since it is a subpage and could be interpreted as step 1 in the install process.  Perhaps our doc page 'Deploy the AppDynamics Operator on Kubernetes' could include a prerequisites section that ensures the steps on 'Install the Cluster Agent' were performed, and make clear that the cluster-agent-operator.yaml was part of the cluster agent bundle downloaded from that step. Jeff @Claudia.Landivar @Ondine.Kilker  ... View more

Hi Surya Can you open a support ticket and reference this post? Jeff ... View more

Also please include your complete require('appdynamics'){...} statement ... View more

Hi Surya Based on the existence of a 'proxy' directory in your app folder: it doesn't appear the libagent: true flag is set to avoid creating the legacy java proxy, which will spin up a JVM in the container that connects with the controller. Using this flag, the embedded node.js agent will run and connect directly to the controller w/o need for a seperate java proxy. You can refer to this sample app and try running it in your environment: https://github.com/Appdynamics/cloudfoundry-apps/blob/master/cf-nodejs/server.js Also, I see that ${process.env.CF_INSTANCE_INDEX} is not being substituted correctly. After setting the libagent flag to true, can you add console.log statements to print out the values to confirm they're correct. You should see the container index substituted. For example... var appdynamics = require("appdynamics").profile({ controllerHostName: appdService['host-name'], controllerPort: appdService['port'], controllerSslEnabled: appdService['ssl-enabled'], accountName: appdService['account-name'], accountAccessKey: appdService['account-access-key'], nodeName: `${appEnv.name}.${process.env.CF_INSTANCE_INDEX}`, libagent: true }); console.log('host : ' + appdService['host-name']) console.log('port : ' + appdService['port']) console.log('ssl: ' + appdService['ssl-enabled']) console.log('account: ' + appdService['account-name']) console.log('node : ' + `${appEnv.name}.${process.env.CF_INSTANCE_INDEX}`) prints out: 2018-12-10T10:21:44.31-0800 [APP/PROC/WEB/0] OUT host : ...appdynamics.com 2018-12-10T10:21:44.32-0800 [APP/PROC/WEB/0] OUT port : 80 2018-12-10T10:21:44.32-0800 [APP/PROC/WEB/0] OUT ssl: false 2018-12-10T10:21:44.32-0800 [APP/PROC/WEB/0] OUT account: customer1 2018-12-10T10:21:44.32-0800 [APP/PROC/WEB/0] OUT node : appd-node-demo.0 Please post the output from these log statements, as well as the agent logs. ... View more

Hi Surya Are you able to ssh into the container and check the logs at /tmp/appd? They may not exist if the agent didn't start up correctly. Since a proxy is required, you'd want to use the Node.js agent specific settings (proxyHost, proxyPort), which you'd set in the require statement (see example below). Doc link: https://docs.appdynamics.com/display/PRO45/Node.js+Settings+Reference Also, you'll want to explicitly set the other AppD settings from your user provided service in the require statement. The example below is based on a marketplace service and environment variables for app and tier name, so you'll have to adapt it to pull the values from the user provided service (based on how it's stored in VCAP_SERVICES). There some more info here: https://github.com/cloudfoundry-community/node-cfenv Add as dependency: "cfenv" :  "latest" , Also note that nodeName is set to explicitly append the instance id to guarantee a unique node name when you scale and libagent:true will enable the embedded/proxyless agent. var cfEnv = require( 'cfenv' ); var appEnv = cfEnv.getAppEnv(); var appdService = appEnv.getServiceCreds( 'pcf-appd-instance' ); var appdynamics = require( "appdynamics" ).profile({      controllerHostName: appdService[ 'host-name' ],      controllerPort: appdService[ 'port' ],      controllerSslEnabled: appdService[ 'ssl-enabled' ],      accountName: appdService[ 'account-name' ],      accountAccessKey: appdService[ 'account-access-key' ],      applicationName: `${process.env.APPD_APP_NAME}`,      tierName: `${process.env.APPD_TIER_NAME}`,      nodeName: `${appEnv.name}.${process.env.CF_INSTANCE_INDEX}`,      libagent:  true,      proxyHost: x,      proxyPort: y }); ... View more