There has been a few announcements lately regarding Cisco's Container Platform (a.k.a: CCP) and they've all been good. Having integration with AWS allows CCP to deploy Kubernetes clusters on vSphere or EKS from the same control point. But another great integration that's been there for the last few months is the App Dynamics (AppD) Kubernetes support announced earlier this year.
Let's show how we can make this AppD work on top of CCP!
Step 1: Get a CCP Kubernetes cluster up and running
If you have CCP then you are golden, spin up a new cluster and it just works!
If you don't have CCP you can try it out in two easy ways:
If you have vSphere 6.5 and nodes running in HA mode on a servers with processors at a minimum of IvyBridge then you can download the 90 day trial versions and get them running. The install can be done in under an hour.
If you don't have an environment, use the Cisco Sandbox! You can spin up a container platform in just a few clicks and have it for several hours. Plenty to get going with!
Step 2: Install AppD Controller Console
We'll be running the controller console onprem. AppD also has a SaaS based offering that is simpler to get going quickly. Let's show how we can install this onPrem.
This will return an obscene string that is too offensive to print here... well actually no, its just a long meaningless string to identify my future requests to the server and authenticate. With this token we can do:
Now to get the bits we use the token and the URL we fetched above:
Step 3: Install the Enterprise Controller and Events Service
Now we want to add the console. You can follow the simple install using the GUI:
Choose Express InstallName the ControllerEnter credentials
You can use this method and it works pretty well. It will take a while for the machine to install. I found, however that it doesn't give all the error messages that you may need in a demo environment. I instead followed the command line instructions:
This job took 9 minutes and 18 seconds to install. It failed originally because I didn't have enough RAM on the virtual machine.
You should now be able to log into this service at port :8090 (in my case with admin / CIsco.123 ). Also notice that the controllerAdminPassword should be different than the controllerRootUserPassword.
When complete the Event Service and Controller service should be running.
You'll need to obtain a license file from your friendly AppD account team. The license (named license.lic) should be placed in the controller subdirectory. In my case I put it in /opt/appdynamics/controller/controller.
You can then see what you were licensed for by examining the settings / licensing:
4. AD Capital Kubernetes Monitoring
To show how AppDynamics can monitor Kubernetes we'll install a sample application called AD Capital. To get this you can run:
kubectl create -f .
This may take several minutes for the containers to download and for the agents to register in AppD. You can check on the status by running
kubectl get pods -o wide -w
When finished you should be able to see them in the AppD application console
4.4 Deploy Machine Agents
We can also deploy the machine agents on Kubernetes
kubectl create -f monitor-deployment.yaml
A daemon set will be installed on every kubernetes VM to give machine monitoring information like CPU or Memory usage
appD Machine Agents
At this point our apps and our Kubernetes cluster is all set up with AppD ready to monitor and get insight into the applications that are running on Cisco Container Platform.
In this blog post we showed how to install AppD and then show a sample application on Kubernetes. We also showed how machine agents can be installed. The Github repository we referenced has more information and ideas you could try to get more visibility into your CCP Kubernetes cluster and the containers running on top of it. We highly recommend reading through that document as the most difficult part of filling out the environment variables and bringing up a Kubernetes cluster has been complete!
Hi, I have a question about the UCSM Capability Catalog and CPUs, to help with my understanding. We have purchased some new M5 blades with 2nd-gen Intel Scalable processors (UCS-CPU-I6248R). My understanding was that the 4.0 firmware supported...
The "Get-UcsMemoryUnit" command provides lots of information, but not the PID. I read somewhere that "Get-UcsCapability" is supposed to provide the PID for the associated ManagedObject but it does not appear to accept Cisco.Ucsm.MemoryUnit even thoug...