<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Merge a Web Request Service and a Web Service into a single service in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283318#M37292</link>
    <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/79246"&gt;@VictorRuiz&lt;/a&gt;&amp;nbsp;It's not possible with the service detection v1. However, I think this could be possible using the recently added &lt;A href="https://docs.dynatrace.com/docs/shortlink/service-service-detection-v2" target="_blank"&gt;service detection v2&lt;/A&gt;. (TBH - I did not try that).&lt;BR /&gt;&lt;BR /&gt;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.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Aug 2025 17:49:04 GMT</pubDate>
    <dc:creator>Julius_Loman</dc:creator>
    <dc:date>2025-08-07T17:49:04Z</dc:date>
    <item>
      <title>Merge a Web Request Service and a Web Service into a single service</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283183#M37269</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;In my environment, I have a Process Group that contains two services: one identified as a&amp;nbsp;Web Request Service&amp;nbsp;and another as a&amp;nbsp;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.&lt;BR /&gt;&amp;nbsp;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.&lt;BR /&gt;&amp;nbsp;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?&lt;BR /&gt;&amp;nbsp;I appreciate any guidance or experience you can share.&lt;/P&gt;
&lt;P&gt;Thank you!&lt;BR /&gt;Victor&lt;/P&gt;</description>
      <pubDate>Thu, 07 Aug 2025 06:05:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283183#M37269</guid>
      <dc:creator>VictorRuiz</dc:creator>
      <dc:date>2025-08-07T06:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: Merge a Web Request Service and a Web Service into a single service</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283184#M37270</link>
      <description>&lt;P&gt;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.&lt;BR /&gt;&lt;BR /&gt;We typically see this with separate technologies serving different types of requests:&lt;BR /&gt;&amp;nbsp;- Web Service = static content, web server redirects, etc&lt;BR /&gt;&amp;nbsp;- Web Request Service = dynamic content flowing through to back-end applications/adapters&lt;BR /&gt;&lt;BR /&gt;Another great answer here =&amp;gt;&amp;nbsp;&lt;A href="https://community.dynatrace.com/t5/Open-Q-A/Difference-between-Web-service-and-Web-request-service/m-p/168618/highlight/true#M17686" target="_blank"&gt;https://community.dynatrace.com/t5/Open-Q-A/Difference-between-Web-service-and-Web-request-service/m-p/168618/highlight/true#M17686&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Aug 2025 13:59:25 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283184#M37270</guid>
      <dc:creator>m3tomlins</dc:creator>
      <dc:date>2025-08-06T13:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: Merge a Web Request Service and a Web Service into a single service</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283278#M37284</link>
      <description>&lt;DIV&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Thank you for your explanation and the references.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;In my context, I have two services: a&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Web Service&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;and a&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Web Request Service&lt;/STRONG&gt;&lt;SPAN&gt;. Based on the documentation you shared, it seems Dynatrace separates them because they are different technologies:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Web Request Services&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;= typical web requests (HTTP/HTTPS from web applications)&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Web Services&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;= SOAP services defined by WSDL&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;P&gt;Even though both are running within the same microservice (process group), Dynatrace detects and displays them as separate services.&lt;/P&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Please find attached the screenshots with the properties of both services and the process group for your reference.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;Web service:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="VictorRuiz_0-1754556429072.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/29433iA9656B0348E119C7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="VictorRuiz_0-1754556429072.png" alt="VictorRuiz_0-1754556429072.png" /&gt;&lt;/span&gt;&lt;P&gt;&lt;SPAN&gt;Web request service:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="VictorRuiz_1-1754556468342.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/29434iB302ED130A887943/image-size/medium?v=v2&amp;amp;px=400" role="button" title="VictorRuiz_1-1754556468342.png" alt="VictorRuiz_1-1754556468342.png" /&gt;&lt;/span&gt;&lt;P&gt;PGI:&lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="VictorRuiz_2-1754556535499.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/29435i90C2425AF8765956/image-size/medium?v=v2&amp;amp;px=400" role="button" title="VictorRuiz_2-1754556535499.png" alt="VictorRuiz_2-1754556535499.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;STRONG&gt;My objective is to merge both services into a single service entity, if possible.&lt;/STRONG&gt;&lt;BR /&gt;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.&lt;/P&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Is it possible to merge these two services in Dynatrace, or is this separation a technical limitation due to the detection mechanisms?&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;P&gt;If there is any workaround or best practice for achieving a unified view, I would really appreciate your advice.&lt;/P&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Thank you in advance for your help!&lt;BR /&gt;&lt;BR /&gt;Victor&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 07 Aug 2025 08:49:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283278#M37284</guid>
      <dc:creator>VictorRuiz</dc:creator>
      <dc:date>2025-08-07T08:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: Merge a Web Request Service and a Web Service into a single service</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283318#M37292</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/79246"&gt;@VictorRuiz&lt;/a&gt;&amp;nbsp;It's not possible with the service detection v1. However, I think this could be possible using the recently added &lt;A href="https://docs.dynatrace.com/docs/shortlink/service-service-detection-v2" target="_blank"&gt;service detection v2&lt;/A&gt;. (TBH - I did not try that).&lt;BR /&gt;&lt;BR /&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Aug 2025 17:49:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Merge-a-Web-Request-Service-and-a-Web-Service-into-a-single/m-p/283318#M37292</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2025-08-07T17:49:04Z</dc:date>
    </item>
  </channel>
</rss>

