# Openshift Kubernetes process group naming issue

**URL:** <https://community.dynatrace.com/t/openshift-kubernetes-process-group-naming-issue/49424>\
**Category:** Container platforms\
**Tags:** installation, openshift, tagging, oneagent, processes, infrastructure-operations, kubernetes\
**Created:** [December 18, 2024, 4:57pm UTC](https://community.dynatrace.com/t/openshift-kubernetes-process-group-naming-issue/49424 "2024-12-18T16:57:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vinnu\_arige\_moe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/vinnu_arige_moe/32/8903_2.png) [@vinnu\_arige\_moe](https://community.dynatrace.com/u/vinnu_arige_moe)\
**Post date:** [December 18, 2024, 4:57pm UTC](https://community.dynatrace.com/t/openshift-kubernetes-process-group-naming-issue/49424/1 "2024-12-18T16:57:04Z")

</div>

We have openshift platform and our&nbsp; 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.

![Screenshot 2024-12-18 at 10.55.19 AM.png](https://global.discourse-cdn.com/dynatrace/original/3X/e/f/ef981a94e9fdcb82926c1106a9a38684a7a6d279.png)

![Screenshot 2024-12-18 at 10.55.27 AM.png](https://global.discourse-cdn.com/dynatrace/original/3X/5/c/5ce0b4ecb648a5de4d48e6c1783b98d387848055.png)

---

<div class="post-metadata">

**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\
**Post date:** [December 19, 2024, 6:32am UTC](https://community.dynatrace.com/t/openshift-kubernetes-process-group-naming-issue/49424/2 "2024-12-19T06:32:02Z")

</div>

Hi&nbsp;[@vinnu\_arige\_moe](https://community.dynatrace.com/user/30293)

PFA helpful resources.

- Proceed with process group detection rules as it impact both the detection and naming as well:&nbsp;[Process group detection — Dynatrace Docs](https://docs.dynatrace.com/docs/observe/infrastructure-monitoring/process-groups/configuration/pg-detection)
- On the service detection and naming level :&nbsp;[Configure service detection rules in Service Detection v1 — Dynatrace Docs](https://docs.dynatrace.com/docs/observe/applications-and-microservices/services/service-detection-and-naming/customize-service-detection)

Hoping it adds value.

BR,

Peter

---

<div class="post-metadata">

**Author:** ![PetrVlacil](https://avatars.discourse-cdn.com/v4/letter/p/54ee81/32.png) [@PetrVlacil](https://community.dynatrace.com/u/PetrVlacil)\
**Post date:** [December 19, 2024, 10:00am UTC](https://community.dynatrace.com/t/openshift-kubernetes-process-group-naming-issue/49424/3 "2024-12-19T10:00:37Z")

</div>

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:

 ![Screenshot 2024-12-19 104232.png](https://global.discourse-cdn.com/dynatrace/original/2X/8/85ec5624ffecd01e9c0eb8a96ca58772935d0805.png)

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

 ![Screenshot 2024-12-19 103829.png](https://global.discourse-cdn.com/dynatrace/original/3X/8/6/8638f9137e7d100deb6642604f8eee02f81297ff.png)

Hope that helps
