06 Aug 2025
02:47 PM
- last edited on
07 Aug 2025
07:05 AM
by
MaciejNeumann
Hi everyone,
In my environment, I have a Process Group that contains two services: one identified as a Web Request Service and another as a Web Service. I would like to know if it is possible to merge both into a single service, since they both belong to the same process and are closely related.
So far, I have only created a detection rule under "Service detection rules for Full Web Requests," but this has not resulted in both services being grouped as one. They still appear as separate entities.
Is there any way to group them into a single service? Should I create a different type of rule, or is there a limitation in Dynatrace that prevents this kind of merge?
I appreciate any guidance or experience you can share.
Thank you!
Victor
Solved! Go to Solution.
06 Aug 2025 02:57 PM - edited 06 Aug 2025 02:59 PM
Hi Victor - is there any chance you could share the properties of the 2 services and the underlying Process Group? That would help analyze what's going on there.
We typically see this with separate technologies serving different types of requests:
- Web Service = static content, web server redirects, etc
- Web Request Service = dynamic content flowing through to back-end applications/adapters
Another great answer here => https://community.dynatrace.com/t5/Open-Q-A/Difference-between-Web-service-and-Web-request-service/m...
07 Aug 2025 09:49 AM
Hi,
Even though both are running within the same microservice (process group), Dynatrace detects and displays them as separate services.
Web request service:
PGI:
My objective is to merge both services into a single service entity, if possible.
The main reason is to have all relevant information (failure rate, response time, etc.) in one place. For our technical team, it is quite challenging to get a clear view of the health of the microservice when the related data is split across two different services.
If there is any workaround or best practice for achieving a unified view, I would really appreciate your advice.
07 Aug 2025 06:49 PM
@VictorRuiz It's not possible with the service detection v1. However, I think this could be possible using the recently added service detection v2. (TBH - I did not try that).
Anyway, I recommend keeping those services separate. In the application itself, those two are in fact two different endpoints, although they share a common URL path prefix for example.