topic Split services based on Kubernetes Cluster they are running in Container platforms

Split services based on Kubernetes Cluster they are running

Theodore_x86 — Tue, 13 Feb 2024 22:41:10 GMT

Hello.

We have two identical AKS clusters with deployed the exact applications/services. As expected, Dynatrace wraps all the above apps to the same process group/service.

We want to distinguish the services based on the AKS they are running. However, on process detection rules there is no condition based on Kubernetes Cluster ID. My best guess is to assign AKS nodes to different host groups so that different process groups are created. I am not quite sure if this is even going to work, since AKS nodes are more of an abstract layer rather that common hosts.

Any better idea to tune this than the "host group" concept?

Re: Split services based on Kubernetes Cluster they are running

Yosi_Neuman — Wed, 14 Feb 2024 06:27:50 GMT

Hi @Theodore_x86

IMO You can use the Group filed in the k8s installation page

Which will add the arg --set-host-group=first to the dynakub.yaml

And also a network zone will be crated under this name.

HTH

Yos

Re: Split services based on Kubernetes Cluster they are running

PacoPorro — Wed, 14 Feb 2024 08:29:47 GMT

Also, you can use the DT_RELEASE_STAGE and DT_RELEASE_PRODUCT env variables.

https://docs.dynatrace.com/docs/shortlink/workload-detection#workload-detection-rules-for-kubernetes

Re: Split services based on Kubernetes Cluster they are running

Theodore_x86 — Wed, 14 Feb 2024 10:00:54 GMT

Thanks Yosi. We are not using the direct "Deploy Dynatrace" page, since we go for the CloudNativeFullStack deployment. But it's basically the same thing, it just creates the yaml for you.

Theodore

Re: Split services based on Kubernetes Cluster they are running

DynaGibbo — Thu, 15 Feb 2024 00:47:53 GMT

We had the same issue when we moved to cloud native full stack and kubernetes cluster isn't a field you can distinguish services on.
Our solution was to inject the set-host-group value into the dynatrace CRD, specifically the cloud

eg.

apiVersion: dynatrace.com/v1beta1

kind: DynaKube

metadata:

name: dynakube

namespace: dynatrace

annotations:

feature.dynatrace.com/automatic-kubernetes-api-monitoring: "true"

feature.dynatrace.com/enable-activegate-authtoken: "true"

feature.dynatrace.com/max-csi-mount-attempts: "3"

spec:

customPullSecret: dynakube-pull-secret

apiUrl: https://{environmentid}.live.dynatrace.com/api

oneAgent:

cloudNativeFullStack:

args:

- "--set-host-group=###"

Re: Split services based on Kubernetes Cluster they are running

Theodore_x86 — Mon, 26 Feb 2024 11:22:50 GMT

Yes exactly, that is what we did also eventually. Host group is the solution ultimately.