topic Re: Openshift K8s process group naming issue in Container platforms

Openshift Kubernetes process group naming issue

vinnu_arige_moe — Wed, 17 Dec 2025 12:39:57 GMT

We have openshift platform and our process group naming is getting grouped up with all the services with different env

In single namespace X and with workload name app1-env1, app1-env2, app1-env3. So when we go to service name X-service we are seeing all the workload getting combined and also single process group for all the workload & env.

In our openshift environment we have lanes which are called as env1-env6 and developer deploy their app in these lanes.

We wanted to separate our the process group and service based on the workload/env.

Re: Openshift K8s process group naming issue

Peter_Youssef — Thu, 19 Dec 2024 06:32:02 GMT

Hi @vinnu_arige_moe

PFA helpful resources.

Proceed with process group detection rules as it impact both the detection and naming as well: https://docs.dynatrace.com/docs/observe/infrastructure-monitoring/process-groups/configuration/pg-detection
On the service detection and naming level : https://docs.dynatrace.com/docs/observe/applications-and-microservices/services/service-detection-and-naming/customize-service-detection

Hoping it adds value.

BR,

Peter

Re: Openshift K8s process group naming issue

PetrVlacil — Thu, 19 Dec 2024 10:00:37 GMT

Hello,

we had similar setup. Different app environments in one namespace, environment stated in the workload name. It is not the proper way to separate environments, but we solved it by redeploying all the pods so they have specific environment variables:

DT_RELEASE_PRODUCT
DT_RELEASE_STAGE
DT_RELEASE_VERSION

We put env value into the DT_RELEASE_STAGE, name of the deployed app into the DT_RELEASE_PRODUCT and version in DT_RELEASE_VERSION.

This way processes in containers have those environment variables. Dynatrace uses them for Release detection and you can configure "Cloud application and workload detection rule" to use stage and product for process grouping.

This is how the process properties looks like after deployment:

And here is the rule configuration: in Settings > Processes and containers > Cloud application and workload detection:

Hope that helps