<?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 report for service requests based on dynamic request content in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/report-for-service-requests-based-on-dynamic-request-content/m-p/122046#M13925</link>
    <description>&lt;P&gt;Hi, we are looking to get the count and response time for dynamic web requests by capturing &amp;amp; bucketing by the dynamic value. Looks like there are is challenge with this:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;global privacy setting to mask client IP addresses, URIs, and HTTP post parameters is on, hence the dynatrace is masking the dynamic part of the web/service request&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Is there a workaround to configure this ? Please see screenshot:&lt;/P&gt;&lt;P&gt;The request pattern is something like:&lt;/P&gt;&lt;PRE&gt;/sites/ESCNNNNNN/.*/.*.aspx&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/28326-1614082498031.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Feb 2021 12:16:57 GMT</pubDate>
    <dc:creator>rswarnka</dc:creator>
    <dc:date>2021-02-23T12:16:57Z</dc:date>
    <item>
      <title>report for service requests based on dynamic request content</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/report-for-service-requests-based-on-dynamic-request-content/m-p/122046#M13925</link>
      <description>&lt;P&gt;Hi, we are looking to get the count and response time for dynamic web requests by capturing &amp;amp; bucketing by the dynamic value. Looks like there are is challenge with this:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;global privacy setting to mask client IP addresses, URIs, and HTTP post parameters is on, hence the dynatrace is masking the dynamic part of the web/service request&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Is there a workaround to configure this ? Please see screenshot:&lt;/P&gt;&lt;P&gt;The request pattern is something like:&lt;/P&gt;&lt;PRE&gt;/sites/ESCNNNNNN/.*/.*.aspx&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/28326-1614082498031.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 12:16:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/report-for-service-requests-based-on-dynamic-request-content/m-p/122046#M13925</guid>
      <dc:creator>rswarnka</dc:creator>
      <dc:date>2021-02-23T12:16:57Z</dc:date>
    </item>
    <item>
      <title>Re: report for service requests based on dynamic request content</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/report-for-service-requests-based-on-dynamic-request-content/m-p/122047#M13926</link>
      <description>&lt;P&gt;Create a request attribute (RA) to grab that portion of the URL. During creation there's a checkbox that allows the RA to access unmasked data. This process is similar to what you've already done for your Business Transaction RA.&lt;/P&gt;&lt;P&gt;Then create a calculated service metric (settings &amp;gt; server-side service monitoring &amp;gt; calculated service metrics) with a condition where your request attribute exists. Split by the request attribute itself.&lt;/P&gt;&lt;P&gt;At this point you have a metric split by each request attribute value (eg. ESC111511) and you can chart it using hte Metrics view and / or alert on it using "custom events for alerting" (settings &amp;gt; anomaly detection &amp;gt; custom events for alerting)&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 05:54:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/report-for-service-requests-based-on-dynamic-request-content/m-p/122047#M13926</guid>
      <dc:creator>adam_gardner</dc:creator>
      <dc:date>2021-02-24T05:54:53Z</dc:date>
    </item>
  </channel>
</rss>

