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.
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
Featured Posts
