<?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 Do Service Request URL cleanup rules and naming rules not work together? in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Do-Service-Request-URL-cleanup-rules-and-naming-rules-not-work/m-p/123296#M14405</link>
    <description>&lt;P&gt;Hi, I am working on adding a request attribute to the request name for a group of service requests. I am running into an issue where some previously implemented URL cleanup rules don't work when the request naming rule is implemented.&lt;/P&gt;&lt;P&gt;The URL cleanup rules were removing a token that wasn't needed in our request names. &lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21954-1568820675733.png" /&gt;&lt;/P&gt;&lt;P&gt;The request naming rule adds a request attribute called &lt;STRONG&gt;pyActivity&lt;/STRONG&gt; to the end of the request.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21955-1568820824922.png" /&gt;We want to be able to have the request name remove the token found in the URL, and add the request attribute to the end  of the request. Below are the rules I am currently using to try to cleanup URL and add the request attribute.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;URL Cleanup Rule:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21956-1568820986184.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Request Naming Rule:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21957-1568821035510.png" /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Anyone know if there is a way to make these two rules work together for our request names?&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 18 Sep 2019 15:41:03 GMT</pubDate>
    <dc:creator>adam_sjoerdsma</dc:creator>
    <dc:date>2019-09-18T15:41:03Z</dc:date>
    <item>
      <title>Do Service Request URL cleanup rules and naming rules not work together?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Do-Service-Request-URL-cleanup-rules-and-naming-rules-not-work/m-p/123296#M14405</link>
      <description>&lt;P&gt;Hi, I am working on adding a request attribute to the request name for a group of service requests. I am running into an issue where some previously implemented URL cleanup rules don't work when the request naming rule is implemented.&lt;/P&gt;&lt;P&gt;The URL cleanup rules were removing a token that wasn't needed in our request names. &lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21954-1568820675733.png" /&gt;&lt;/P&gt;&lt;P&gt;The request naming rule adds a request attribute called &lt;STRONG&gt;pyActivity&lt;/STRONG&gt; to the end of the request.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21955-1568820824922.png" /&gt;We want to be able to have the request name remove the token found in the URL, and add the request attribute to the end  of the request. Below are the rules I am currently using to try to cleanup URL and add the request attribute.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;URL Cleanup Rule:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21956-1568820986184.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Request Naming Rule:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/21957-1568821035510.png" /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Anyone know if there is a way to make these two rules work together for our request names?&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Sep 2019 15:41:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Do-Service-Request-URL-cleanup-rules-and-naming-rules-not-work/m-p/123296#M14405</guid>
      <dc:creator>adam_sjoerdsma</dc:creator>
      <dc:date>2019-09-18T15:41:03Z</dc:date>
    </item>
    <item>
      <title>Re: Do Service Request URL cleanup rules and naming rules not work together?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Do-Service-Request-URL-cleanup-rules-and-naming-rules-not-work/m-p/123297#M14406</link>
      <description>&lt;P&gt;The issue is that you are using URL:path in naming rule. Cleanup rule does not change url path, it is changing request name. (when you go to purepath, you will see full path there without cleanups). There is no placeholder that may use current url name so it may be difficult to make it work like you want. It is good point for product IDEA for adding another placeholder (current name). &lt;/P&gt;&lt;P&gt;Sebastian&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Sep 2019 17:58:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Do-Service-Request-URL-cleanup-rules-and-naming-rules-not-work/m-p/123297#M14406</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2019-09-18T17:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: Do Service Request URL cleanup rules and naming rules not work together?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Do-Service-Request-URL-cleanup-rules-and-naming-rules-not-work/m-p/123298#M14407</link>
      <description>&lt;P&gt;Thanks Sebastian! I will go ahead and setup an RFE for using "Current Name" as a placeholder for the request naming rules.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Sep 2019 19:00:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Do-Service-Request-URL-cleanup-rules-and-naming-rules-not-work/m-p/123298#M14407</guid>
      <dc:creator>adam_sjoerdsma</dc:creator>
      <dc:date>2019-09-18T19:00:24Z</dc:date>
    </item>
  </channel>
</rss>

