topic Re: Dynatrace Process group in Container platforms

Dynatrace Process group

ahadnoor — Mon, 03 Apr 2023 11:59:34 GMT

Hello,

I want to merge all the different deployment config pods log to one Process group. The deployment configs naming convention is like <application_name>-<version>-<date><month>. For example hello-world-v1-1-0-20mar, hello-world-v1-2-0-21apr, hello-world-v1-3-0-22may.

To achieve that I created an advanced detection rule but still it's not working. I have tried chnaging the value such as hello-world-v, hello-world-v*, hello-world-. But none of them worked. One agent automatically define the Kubernetes base Pod name like: <application_name>-v*-*<month>. I know I can represent the month value as digit by why DT not replacing the month value with an asterisk as well?

Re: Dynatrace Process group

Romanenkov_Al3x — Mon, 03 Apr 2023 07:53:43 GMT

Hello.

For several Customers to avoid problems with automatic rules we control Process Groups with Environment variable DT_CLUSTER_ID.

With this approach we don't need additional rules, and for Application teams it is also very simple to define and manage.

Maybe to try with Process Group extraction rules, to try extract and have this process group name "hello-world" instead hello-world-v*-*-*-*mar. (test-deployment-k*c-t*n)

Also if it possible I will be try with different settings for namespace in "Settings > Processes and containers > Cloud application and workload detection"

Regards,

Alex Romanenkov

Re: Dynatrace Process group

paolo_fumanelli — Mon, 03 Apr 2023 09:42:24 GMT

Unfortunately there's no way to modify the extracted content. You can just make it ignore the month by putting a placeholder as first char and before the month itself. For example let

hello-world-v1-3-0-22may

become

#hello-world-v1-3-0-22#may

And then in extraction rule delimit name between # and # so it will become

hello-world-v*-*-*-* for all of them

Re: Dynatrace Process group

ahadnoor — Tue, 04 Apr 2023 02:52:31 GMT

Hello,
Thank you for your reply. Unfortunately, it didn't work. As the base pod name gets changed every time it creates a new process group with the same name but a different kubernetes base pod name.

Re: Dynatrace Process group

ahadnoor — Tue, 04 Apr 2023 02:56:34 GMT

Hello,

Thank you for your reply. Could you please elaborate on where I have to define the Placeholder? In Advance Detection Rule?

Re: Dynatrace Process group

ahadnoor — Tue, 04 Apr 2023 06:25:41 GMT

"Settings > Processes and containers > Cloud application and workload detection" solve the issue