Hello Gustavo, Yes, by default SaaS controller is SSL enabled so we need to provide secure connection otherwise Clusteragent will fail to connect to the controller. Glad that helped.  Best Regards, Rajesh Ganapavarapu ... View more

Hello @Gustavo.Marconi , Sure I'm checking on running the curl command to check the connectivity issue. I remember asking you to update the controller url as https instead of http ? Have you made these change and still facing the same issue ? Also can you please confirm if you have any proxy inbetween ? Best Regards, Rajesh Ganapavarapu ... View more

Hello @Michael.Mom, In addition to @MARTINA.MELIANA, if you would like to monitor the AWS RDS SQL Server instance hardware metrics you can install the machine agent on that server and you will be able to monitor hardware metrics. You may visit the below pages for more understanding. https://docs.appdynamics.com/appd/24.x/24.7/en/infrastructure-visibility https://docs.appdynamics.com/appd/24.x/24.7/en/infrastructure-visibility/overview-of-infrastructure-visibility https://docs.appdynamics.com/appd/24.x/24.7/en/infrastructure-visibility/hardware-resources-metrics Best Regards, Rajesh Ganapavarapu ... View more

Hello @Gustavo.Marconi , Yes, you should have the full rights to install the curl on the pod. Can you check the network connection by running curl after the curl installation ? Best Regards, Rajesh ... View more

Hello @Gustavo.Marconi, Thank you for contacting us. Looks like the access key is not setup properly. Can you please confirm if you have created the access key correctly ? You can run the below command and check if you have setup the access key  or not. kubectl get secret cluster-agent-secret -n appdynamics -o jsonpath='{.data.controller-key}' | base64 --decode Also can you please confirm the agent version and the operator version that you're deploying ?   If you are using lessthan 23.11 version I would recommend you to dopwnload the latest version.   Could you please follow below: Download the latest version if the current version is 23.11 or less. Delete old Controller Access Key Secret: Create Controller Access Key Secret:  kubectl -n appdynamics create secret generic cluster-agent-secret --from-literal=controller-key=<access-key> Give a try and let me know how it goes. Happy Friday and weekend. Best Regards, Rajesh Ganapavarapu   ... View more

Hello @sajo.sam, The error message you've encountered "agentregistrationmodule.go:132 - clusterId: -1" indicates that the cluster agent received incorrect controller information or that the controller is rejecting the registration. To verify if you've configured the correct controller access key, you can execute the following command: kubectl get secret cluster-agent-secret -n appdynamics -o jsonpath='{.data.controller-key}' | base64 --decode Please note that DONOT share any controller sensitive information in this public platform.   Regarding the error mentioned in your comments: [ERROR]: 2024-04-09 11:21:08 - agentregistrationmodule.go:131 - Failed to send agent registration request: Post "accountname.saas.appdynamics.com:8080/sim/v2/agent/clusterRegistration": context deadline exceeded (Client.Timeout exceeded while awaiting headers) This is likely due to a network connection issue. You can check the network connection from one of the running pods using the following command: curl -v -k -u singularity-agent@<accountname>  https://<controllerhost>.saas.appdynamics.com:<port>/sim/v2/agent/clusterRegistration   Please check the above if that helpful. Best Regards, Rajesh Ganapavarapu ... View more

Hello Shubham, In addition to Ryan suggestion, I'm posting more useful links for your ref if incase those may help. Please note AppDynamics moved extensions under an open-source model, to enable customers to directly evolve them to suit their needs / build new use cases, you can find more information  https://docs.appdynamics.com/display/PAA/Support+Advisory%3A+Changes+to+Extensions+Support+ModelWe have also documented answers to most common extension queries along with troubleshooting tips and tricks in the following links. Extensions troubleshooting Advanced Extensions Troubleshooting Best Regards, Rajesh Ganapavarapu ... View more

Hello @sajo.sam , This error message we see when there is an incorrect controller information passed.  You may check the access key by running this below command. kubectl get secret cluster-agent-secret -n appdynamics -o jsonpath='{.data.controller-key}' | base64 --decode Also please check the network connection Run the following command to check the connection curl -v -k -u singularity-agent@dtvnprod:<access_key> https://dtvnprod.saas.appdynamics.com:443/sim/v2/agent/clusterRegistration Hope this helps. Best Regards, Rajesh Ganapavarapu ... View more

There could be several reasons for failure. Please verify whether your environment is utilizing a Docker runtime built on ContainerD or a similar platform. If your intended machine agent is v22.3.0, it only supports Docker runtime exclusively. Additionally, ensure that the user has access to /run/docker.sock . You can check this by running: bash cat /run/docker.sock In past instances, this issue occurred due to either no running containers or permission problems. You can diagnose this with the following command:   sudo curl -s -S -i --unix-socket /var/run/docker.sock http:/info docker info If you're utilizing the containerd runtime, consider upgrading to the latest version, such as 24.3.0 MA. I would recommend you to open a Support ticket for any further help as it involves a lot of debugging. Best Regards, Rajesh Ganapavarapu           ... View more

Hello @Dishant.Mokal , By default, the Machine Agent only monitors containers that have a running APM Agent. You can change this by setting the  sim.docker.monitorAPMContainersOnly  property on the Controller. See Controller Settings for Server Visibility. That's why you are not seeing all the containers running on the docker host. Doc ref: https://docs.appdynamics.com/appd/21.x/21.5/en/infrastructure-visibility/monitor-containers-with-docker-visibility If it is a SaaS controller you should raise a Support ticket to enable or disable the property so that we will work with our OPS team. Best Regards, Rajesh Ganapavarapu ... View more

Hello @Yogesh.Joshi , I would encourage you to open a ticket with debug logs enabled so that one of our MA Support SMEs can help you further. It is hard to comment on the warning message here. How do I submit a Support ticket? An FAQ  If you do submit a ticket and hear back from Support, could you please share any learnings back here as a reply?  Best Regards, Rajesh Ganapavarapu ... View more

Hello @Lynn.Chen , I would encourage you to open a ticket with debug logs enabled so that one of our MA Support SMEs can help you further. It is hard to comment on the warning message here. How do I submit a Support ticket? An FAQ  If you do submit a ticket and hear back from Support, could you please share any learnings back here as a reply?  Best Regards, Rajesh Ganapavarapu ... View more

Hello Radhakrishnan, Thank you for posting us.  Yes, the cluster agent will monitor your entire cluster and provide you the all the important metrics.  The Cluster Agent collects metrics and metadata for the entire cluster, including every node and namespace down to the container level. When you instrument applications with AppDynamics APM Agents, the Cluster Agent allows you to view both Kubernetes and APM metrics for those pods (if both the Cluster Agent and the APM Agents are reporting the data to the same account the Controller). You can use Cluster Agent to: Gain visibility into key Kubernetes metrics and events, and detect uptime and availability issues Diagnose issues that may prevent uptime or scalability issues, such as:  Pod failures and restarts Node starvation Pod eviction threats and pod quota violations Image and storage failures Pending or stuck pods. Bad endpoints: detects broken links between pods and application components Service endpoints in a failed state Missing dependencies (Services, configMaps, Secrets) Track resource usage of pods relative to the declared requests and limits Please find the document link where you can see detailed metrics that would collected by the cluster agent. https://docs.appdynamics.com/appd/23.x/latest/en/infrastructure-visibility/monitor-kubernetes-with-the-cluster-agent/use-the-cluster-agent/cluster-metrics https://docs.appdynamics.com/appd/23.x/latest/en/infrastructure-visibility/monitor-kubernetes-with-the-cluster-agent Other imp links : https://docs.appdynamics.com/appd/23.x/latest/en/infrastructure-visibility/monitor-kubernetes-with-the-cluster-agent/overview-of-cluster-monitoring Please let us know if you would like to set up a call and learn the basic information regarding the agent. We have a CAC option where customers can have a call with our consultants and learn more about it. Best Regards, Rajesh Ganapavarapu ... View more

Hello @Kenny.Yu , Thank you for updating the community with the solution.  Updating this for future audiences with document links. Yes, we have recently added this tierNameStrategy with CA auto instrumentation. Doc Ref: https://docs.appdynamics.com/appd/23.x/latest/en/infrastructure-visibility/monitor-kubernetes-with-the-cluster-agent/auto-instrument-applications-with-the-cluster-agent Best Regards, Rajesh Ganapavarapu ... View more

Hello @Rohan.Vaikkath, The answer to your concern is NO. It is not possible to get only a few metrics that you would like to see from the machine agent. It will run the collector script which is built into the machineagent.jar file which you hit while starting the agent. So we can not restrict the machine agent metrics. @Sunil.Agarwal the files inside the monitor's folder is something related to calculations of how the agent calculates those particular metrics. Best Regards, Rajesh Ganapavarapu ... View more

Hello Justin, By default, the machine agent has been configured to monitor 5 volumes. But this value is configurable.   Could you please take a look at the configuration of volumeMonitorConfig section in the $MACHINE_AGENT_HOME/extensions/ServerMonitoring/conf/ServerMonitoring.yml file? It must be looking like: volumeMonitorConfig:     # maxNumberVolumes specifies the maximum number of volumes that the     # machine agent will monitor. maxNumberVolumes          : 5     # whitelistSelectorRegex specifies the regular expression used to whitelist reported volumes     # by name. A volume with the name matching the regex will always be reported,     # with respect to maxNumberVolumes     whitelistSelectorRegex        : "" This configuration means that the agent will show only 5 volumes by default which you see in your case. You can set a higher value to the  maxNumberVolumes  parameter and then restart the machine agent to see the configured no. of volumes in your machine.   PS: Please note that as mentioned under Volume Metrics section at latest doc    There is no maximum value for maxNumberVolumes parameter in volumeMonitorConfig section in the $MACHINE_AGENT_HOME/extensions/ServerMonitoring/conf/ServerMonitoring.yml file. You can set any value you want. I hope this helps 🙂  Cheers, Rajesh Ganapavarapu ... View more

Hello Maddy, as this is an internal Appdynamics error and harmless to the application, you can simply ignore the error unless you are getting health rule alerts due to this. As shown in my attachment, you can filter out the error by unchecking "Show AppDynamics Exceptions". ... View more