<?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 How to move a Service Request from one Service to Another? in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/How-to-move-a-Service-Request-from-one-Service-to-Another/m-p/296773#M38825</link>
    <description>&lt;P&gt;We have these services on our Exchange hosts that are called "Requests on &amp;lt;hostname&amp;gt;:&amp;lt;port_number&amp;gt;"&lt;/P&gt;
&lt;P&gt;Something like this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DT_Services_Requests_on_Hosts.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/32484i95221B2B7B365A33/image-size/medium?v=v2&amp;amp;px=400" role="button" title="DT_Services_Requests_on_Hosts.png" alt="DT_Services_Requests_on_Hosts.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Inside of this "service" are various incoming requests that should be part of other existing services on the host.&amp;nbsp; For example, we have a bunch of EWS requests that are getting put into this catch-all "Requests on" service instead of the actual EWS app pool service.&amp;nbsp; Basically, most requests are getting properly applied to the proper services, but then others aren't and seem to get pushed into this catch-all service.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Question is&lt;/STRONG&gt;, how do we fix that?&amp;nbsp; We don't really use any custom service rules, so it seems to be the default behavior of Dynatrace that is doing this.&lt;/P&gt;</description>
    <pubDate>Fri, 27 Mar 2026 10:36:26 GMT</pubDate>
    <dc:creator>36Krazyfists</dc:creator>
    <dc:date>2026-03-27T10:36:26Z</dc:date>
    <item>
      <title>How to move a Service Request from one Service to Another?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/How-to-move-a-Service-Request-from-one-Service-to-Another/m-p/296773#M38825</link>
      <description>&lt;P&gt;We have these services on our Exchange hosts that are called "Requests on &amp;lt;hostname&amp;gt;:&amp;lt;port_number&amp;gt;"&lt;/P&gt;
&lt;P&gt;Something like this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DT_Services_Requests_on_Hosts.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/32484i95221B2B7B365A33/image-size/medium?v=v2&amp;amp;px=400" role="button" title="DT_Services_Requests_on_Hosts.png" alt="DT_Services_Requests_on_Hosts.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Inside of this "service" are various incoming requests that should be part of other existing services on the host.&amp;nbsp; For example, we have a bunch of EWS requests that are getting put into this catch-all "Requests on" service instead of the actual EWS app pool service.&amp;nbsp; Basically, most requests are getting properly applied to the proper services, but then others aren't and seem to get pushed into this catch-all service.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Question is&lt;/STRONG&gt;, how do we fix that?&amp;nbsp; We don't really use any custom service rules, so it seems to be the default behavior of Dynatrace that is doing this.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2026 10:36:26 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/How-to-move-a-Service-Request-from-one-Service-to-Another/m-p/296773#M38825</guid>
      <dc:creator>36Krazyfists</dc:creator>
      <dc:date>2026-03-27T10:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to move a Service Request from one Service to Another?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/How-to-move-a-Service-Request-from-one-Service-to-Another/m-p/297035#M38847</link>
      <description>&lt;P&gt;You can fix this by creating service detection rules:&lt;BR /&gt;For this, you have to think about how best you can group the required services in a condition. Also the naming you are getting is not great so you should think of some friendly names or that makes sense for the developers/support person/user.&lt;BR /&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/rule-based-service-detection" target="_blank"&gt;https://docs.dynatrace.com/docs/shortlink/rule-based-service-detection&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/custom-service-names" target="_blank"&gt;https://docs.dynatrace.com/docs/shortlink/custom-service-names&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2026 04:01:52 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/How-to-move-a-Service-Request-from-one-Service-to-Another/m-p/297035#M38847</guid>
      <dc:creator>RohitBisht</dc:creator>
      <dc:date>2026-04-01T04:01:52Z</dc:date>
    </item>
  </channel>
</rss>

