How to merge multiple services of the same process group into a single service entity?

[Raul_rrr]

Hi Community,

I have a process group: Process.Group.ABCD. Within this process group, Dynatrace detects 1 Web Request Service and 6 Web Services. Although they all belong to the same process group, Dynatrace creates them as separate services and captures requests individually across these 7 services.

This makes it challenging to query or monitor them as a single unit, since I need to reference multiple service IDs in DQL queries and dashboards.
Is there a way to configure Service Detection (v2) so that all these services from the same process group (both Web Request Service and Web Services) can be merged into a single service entity?

I have already tried creating a service detection rule scoped to the process group and env tag (we use env:q for UAT and env:p for PROD, since both environments share the same process and service names). However, Dynatrace still creates multiple service entities instead of one merged service.

Any guidance, best practices, or working examples on how to achieve this merged service view in Dynatrace would be greatly appreciated.

[JeanBlanc · Accepted solution]

Hi @Raul_rrr,

From what I’ve seen in Dynatrace documentation and Community discussions, Dynatrace cannot merge Web Request Services and Web Services from the same Process Group into a single entity, even when using Service Detection v2 rules, process group scoping, or environment tags.

This appears to be by design:

• Services are detected based on technical entry points

• Different service types aren’t mergeable via Service Detection (v1 or v2)

• The legacy Merged Services feature is deprecated and doesn’t cover this use case

Suggested approach

If the goal is a unified view, it seems more reliable to aggregate at query or dashboard level rather than trying to force service merging.

Regards,

[Julius_Loman]

Eventually, in mid term with SDv2 Dynatrace moves into a direction of a single service per process group to conceptually align with OpenTelemetry. 

In the meantime, I suggest tagging the services and use tags to find the services in dashboard queries.