<?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: Query for the origins the request are coming in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/Query-for-the-origins-the-request-are-coming/m-p/178301#M1698</link>
    <description>&lt;P&gt;Because of the holidays break many of you would miss this thread - does anyone of you have some tips for this subject?&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jan 2022 14:54:55 GMT</pubDate>
    <dc:creator>Michal_Gebacki</dc:creator>
    <dc:date>2022-01-04T14:54:55Z</dc:date>
    <item>
      <title>Query for the origins the request are coming</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Query-for-the-origins-the-request-are-coming/m-p/177902#M1662</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a way to obtain the origin from where the requests are arriving to a process group?&lt;/P&gt;
&lt;P&gt;By origin I mean a http header with a value identifying if the request comes from the old webpage, the new webpage, one of the many apps, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Sebastian.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 12:13:08 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Query-for-the-origins-the-request-are-coming/m-p/177902#M1662</guid>
      <dc:creator>sbrugnoli</dc:creator>
      <dc:date>2022-01-03T12:13:08Z</dc:date>
    </item>
    <item>
      <title>Re: Query for the origins the request are coming</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Query-for-the-origins-the-request-are-coming/m-p/178301#M1698</link>
      <description>&lt;P&gt;Because of the holidays break many of you would miss this thread - does anyone of you have some tips for this subject?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 14:54:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Query-for-the-origins-the-request-are-coming/m-p/178301#M1698</guid>
      <dc:creator>Michal_Gebacki</dc:creator>
      <dc:date>2022-01-04T14:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: Query for the origins the request are coming</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Query-for-the-origins-the-request-are-coming/m-p/178313#M1700</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/46779"&gt;@sbrugnoli&lt;/a&gt;&amp;nbsp;Depending on your situation, I'd recommend using either &lt;A href="https://www.dynatrace.com/support/help/shortlink/service-backtrace" target="_self"&gt;service backtrace&lt;/A&gt;&amp;nbsp;feature or the multidimensional analysis. Backtrace shows you HTTP &lt;SPAN&gt;referrers directly. With MDA you can split the requests by any common PurePath attribute.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;If your process group has several services and you want to search across them, you can use the&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/shortlink/top-web-requests" target="_self"&gt;top web requests&lt;/A&gt;&amp;nbsp; (which is MDA in fact) and filter on the process group.&lt;BR /&gt;&lt;BR /&gt;If you are not sure, please describe your situation in more detail.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 21:50:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Query-for-the-origins-the-request-are-coming/m-p/178313#M1700</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2022-01-04T21:50:24Z</dc:date>
    </item>
  </channel>
</rss>

