Discussion Feed

Hi Kenneth Most definitely, just need to understand how the code works and how AppD represents it. Looks like one class calling another class. Switch the drop down back to class method where you can search for classes, then search for either entity.PolicyPeriod or PolicyPeriod. I believe you should find what you require here. Check which methods this class has available. And do live previews on this class and method. From your initial post you can look at entity.Submission class as well, which methods it has available. I hope I am making sense:) ... View more

Hi Kenneth. Click on the second tab, it's called tools. This will give you a drop down, to either search for classes/methods. Or another option called method invocations. Choose method invocations, wait a couple seconds. You will see live invocations of that class/method and the actual data within. Check if you can see/find the value you are after ... View more

Hi Kenneth My apologies.you should not use the default live preview option. Navigate to the Transaction Detection rules. Click the + sign, like you are going to add a new rule. However you will not save the rule. It's only to find the data you are after. Choose the POJO option, specify the method and class you had and click on live preview on the required node. Once it starts you need to click on the second tab on the right and choose from the drop down - method invocations. This should return live traffic on the class/method being triggered. Normally gives uou 1-2 invocations. You can then view the data for it, to see if you can find the value you are looking for Let me know if you get stuck. Ciao ... View more

Hi Kenneth   What is the MIDC Setup like, What class and method are you using in the configuration? Can you share that?   The easiest way to test this, is to use the Live Preview functionality, enter the class and method name, then use the Live preview Second tab option called Method Invocations.    With this you can check the actual data being populated live , and configure the collection as it needs to be.   Can you validate that you can see the data you are trying to extract using live preview? ... View more

Thanks Sattha   Can you just confirm a couple of things   1. Which version of K8S are you running? 2. What version of the Cluster Agent Operator are you running? If running version 1.14 or less you should have deployed the Operator with the below YAML File cluster-agent-operator-1.14-or-less.yaml   You can try the below YAML and advise apiVersion: appdynamics.com/v1alpha1 kind: Clusteragent metadata: name: k8s-cluster-agent namespace: appdynamics spec: appName: "SEACMACLUSTER-TH-DEVQA" controllerUrl: "https://xxxxxdev.saas.appdynamics.com" account: "xxxxxdev" image: "my-own-repository.org:5000/appdynamics/cluster-agent:latest" logLevel: Debug logFileSizeMb: 10 logFileBackups: 5 stdoutLogging: "true" serviceAccountName: appdynamics-cluster-agent nsToMonitor: - "appdynamics" - "cma-dev" - "cma-qa" proxyUrl: "http://172.30.60.46:80" proxyUser: "Th-xxxxx\\svc_localapp_dev" # # auto-instrumentation config # instrumentationMethod: Env nsToInstrument: - "appdynamics" - "cma-dev" - "cma-qa" appNameStrategy: manual defaultAppName: SEACMA-TH-NONPROD defaultEnv: JAVA_TOOL_OPTIONS instrumentationRules: - namespaceRegex: cma-dev language: java appName: SEACMA-TH-DEV containerMatchString: .* imageInfo: image: "my-own-repository.org:5000/appdynamics/java-agent:latest" agentMountPath: /opt/appdynamics   ... View more

Hi Sattha   Can you try the below YAML Config     apiVersion: appdynamics.com/v1alpha1 kind: Clusteragent metadata: name: k8s-cluster-agent namespace: appdynamics spec: appName: "SEACMACLUSTER-TH-DEVQA" controllerUrl: "https://xxxxxdev.saas.appdynamics.com" account: "xxxxxdev" image: "my-own-repository.org:5000/appdynamics/cluster-agent:latest" logLevel: Debug logFileSizeMb: 10 logFileBackups: 5 stdoutLogging: "true" serviceAccountName: appdynamics-cluster-agent nsToMonitorRegex: appdynamics|cma-dev|cma-qa proxyUrl: "http://172.30.60.46:80" proxyUser: "Th-xxxxx\\svc_localapp_dev" # # auto-instrumentation config # instrumentationMethod: Env nsToInstrumentRegex: cma-dev|cma-qa appNameStrategy: manual defaultAppName: SEACMA-TH-NONPROD defaultEnv: JAVA_TOOL_OPTIONS instrumentationRules: - namespaceRegex: cma-dev language: java appName: SEACMA-TH-DEV containerMatchString: .* imageInfo: image: "my-own-repository.org:5000/appdynamics/java-agent:latest" agentMountPath: /opt/appdynamics   ... View more

Thanks Sattha   Could you remove all instances of the following from the cluster agent yaml instrumentContainer: first and add the following to each of the 2 instrumentation rules containerMatchString: .*   The redeploy, and check if it instruments the pods now ... View more

Hi Sattha   You have set the appNameStrategy : label And in the instrumentation rules, you state that it should use the below label of the Java pods to name the Application.   Do you have a label in your java app's deployment spec that is named "app"? As it will look for that label to set the Application Name. If it's empty it wont register. Your logs show that the instrumentation rule is matching the pod so the rest seem to be correct. appNameLabel: app   I would suggest to set the following, to just validate testing, before switching back to using labels to set the AppD Application Name     appNameStrategy: manual Change  appNameLabel: app to appName: XXX_DEV                                              appName: XXX_QA   Then redeploy and let us know   Ciao   ... View more