My current cluster-agent.yaml has appName repeated 3 times. I hope there is a way for setting a tiername such that on the report, I can separate the results by cluster, or even better, by namespace. I can put the same k8s deployment in either different k8s namespaces (cheaper) or clusters, and need appd to report on them separately.
========= cluster-agent.yaml =======
spec:
appName: "EPOCH-svc"
image: "docker.io/appdynamics/cluster-agent:latest"
serviceAccountName: appdynamics-cluster-agent
nsToMonitor: [nodejs,dev1,dev2,perf1]
stdoutLogging: "true"
instrumentationMethod: Env
nsToInstrumentRegex: nodejs
defaultAppName: EPOCH-svc
logLevel: "DEBUG"
instrumentationRules:
- namespaceRegex: nodejs
instrumentContainer: select
containerMatchString: epoch-awsmw-offerms-dcp
language: nodejs
appName: EPOCH-svc
imageInfo:
image: "docker.io/appdynamics/nodejs-agent:22.7.0-16-stretch-slim"
It turns out that I have to dig deep into tierNameStrategy and tierName to work with the capability of the deployment pipeline.
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.
Best Regards,
Rajesh Ganapavarapu
Hi @Kenny.Yu,
Thank you for sharing the solution!
It turns out that I have to dig deep into tierNameStrategy and tierName to work with the capability of the deployment pipeline.
Hi @Kenny.Yu,
Thanks for asking your question on the Community. If you have not yet, please check out the Cluster Agent Documentation on our Docs site. https://docs.appdynamics.com/appd/22.x/latest/en/infrastructure-visibility/monitor-kubernetes-with-t...
Please note the navigation on the left side of the page to dive deeper into the right topic area.