topic Re: OneAgent application separation in Open Q&A

OneAgent application separation

eric_holloway — Thu, 03 Aug 2023 19:50:54 GMT

We are currently migrating to DT from another APM solution. In an effort to make standards we have tried to come up with the following mandatory values during OneAgent install:

Host Group = Department
Tag Key = Application
- Value = $AppID-$Application
  (ex: Application: 85648-SearchHelper)
Tag Key = Env
- Value = Dev/Mod/Cap/Prod/etc.
  (ex: Env: Cap)

We have a few applications that have several JVM's (belonging to different applications) running on one host. Is there a way to tag these separately to help these teams find their applications faster? We plan to separate Management Zone's by Host Group (and also control RBAC that way for power users).

Re: OneAgent application separation

AntonPineiro — Thu, 03 Aug 2023 21:58:03 GMT

Hi,

You can define your own process group metadata on process level.

Best regards

Re: OneAgent application separation

Romanenkov_Al3x — Mon, 07 Aug 2023 06:57:33 GMT

Hello.

If you want take a look on process group detection:

https://www.dynatrace.com/support/help/platform-modules/infrastructure-monitoring/process-groups/configuration/pg-detection#process-group-detection

You can create rules for process group "splitting" or "merging".

Also take a look on DT_CLUSTER_ID environment variable. It works amazing for many Customers.

Regards,

Alex Romanenkov