<?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 services using API, rules doesn't work in Dynatrace API</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118854#M2025</link>
    <description>&lt;P&gt;I am comparing the Context_Root value as exactly showing in metadata of service. Also kept under observation for couple of days which turns some more request to receive.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Nov 2020 17:21:59 GMT</pubDate>
    <dc:creator>SROLE1</dc:creator>
    <dc:date>2020-11-12T17:21:59Z</dc:date>
    <item>
      <title>Merge services using API, rules doesn't work</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118852#M2023</link>
      <description>&lt;P&gt;I have tried to merge the services which are belongs to one process group, same context root and same application id but different web server name. I tried to valueOverride for server but rule doesn't get affected. Please suggest below is the rule&lt;/P&gt;
&lt;P&gt;{&lt;!-- --&gt;&lt;/P&gt;
&lt;P&gt;"type": "FULL_WEB_REQUEST",&lt;/P&gt;
&lt;P&gt;"managementZones": [],&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"name": "SOA-XXXX_Merge",&lt;/P&gt;
&lt;P&gt;"description": "Merge the SOA -XXXX service",&lt;/P&gt;
&lt;P&gt;"enabled": true,&lt;/P&gt;
&lt;P&gt;"conditions": [&lt;/P&gt;
&lt;P&gt;{&lt;!-- --&gt;&lt;/P&gt;
&lt;P&gt;"attributeType": "CONTEXT_ROOT",&lt;/P&gt;
&lt;P&gt;"compareOperations": [&lt;/P&gt;
&lt;P&gt;{&lt;!-- --&gt;&lt;/P&gt;
&lt;P&gt;"type": "EQUALS",&lt;/P&gt;
&lt;P&gt;"negate": false,&lt;/P&gt;
&lt;P&gt;"ignoreCase": false,&lt;/P&gt;
&lt;P&gt;"values": [&lt;/P&gt;
&lt;P&gt;"/soa-infra/services/default/XXXX"&lt;/P&gt;
&lt;P&gt;]&lt;/P&gt;
&lt;P&gt;}&lt;/P&gt;
&lt;P&gt;]&lt;/P&gt;
&lt;P&gt;}&lt;/P&gt;
&lt;P&gt;],&lt;/P&gt;
&lt;P&gt;"applicationId": null,&lt;/P&gt;
&lt;P&gt;"contextRoot": null,&lt;/P&gt;
&lt;P&gt;"serverName": {&lt;!-- --&gt;&lt;/P&gt;
&lt;P&gt;"valueOverride": "ABCD_WebServer"&lt;/P&gt;
&lt;P&gt;}&lt;/P&gt;
&lt;P&gt;}&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2022 10:27:10 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118852#M2023</guid>
      <dc:creator>SROLE1</dc:creator>
      <dc:date>2022-09-01T10:27:10Z</dc:date>
    </item>
    <item>
      <title>Re: Merge services using API, rules doesn't work</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118853#M2024</link>
      <description>&lt;P&gt;It looks valid. Are you sure you are comparing to a good value in your condition and you have a good type (FULL_WEB_REQUEST)? &lt;BR /&gt;Just a reminder - it is applied only for new requests from the time the API detection rule has been applied.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2020 16:44:19 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118853#M2024</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2020-11-12T16:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: Merge services using API, rules doesn't work</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118854#M2025</link>
      <description>&lt;P&gt;I am comparing the Context_Root value as exactly showing in metadata of service. Also kept under observation for couple of days which turns some more request to receive.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2020 17:21:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118854#M2025</guid>
      <dc:creator>SROLE1</dc:creator>
      <dc:date>2020-11-12T17:21:59Z</dc:date>
    </item>
    <item>
      <title>Re: Merge services using API, rules doesn't work</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118855#M2026</link>
      <description>&lt;P&gt; DId you try to replace EQUALS to STRING_EQUALS ? I did not notice it at the first sight. Context root is a string, so I guess STRING_EQUALS should the right compare operation to choose.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2020 17:51:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118855#M2026</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2020-11-12T17:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: Merge services using API, rules doesn't work</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118856#M2027</link>
      <description>&lt;P&gt;I tried to change STRING_EQUALS but it is automatically changing value to EQUALS. Even i tried to create new rule but same once I submit request then value is auto changed to EQUALS.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2020 09:17:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118856#M2027</guid>
      <dc:creator>SROLE1</dc:creator>
      <dc:date>2020-11-13T09:17:55Z</dc:date>
    </item>
    <item>
      <title>Re: Merge services using API, rules doesn't work</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118857#M2028</link>
      <description>&lt;P&gt;Below is service type and technology,  where  i am trying this rule. Hope it supports&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Service type&lt;/TD&gt;&lt;TD&gt;Web request service&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Service main technology&lt;/TD&gt;&lt;TD&gt;Oracle WebLogic&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Fri, 13 Nov 2020 11:46:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118857#M2028</guid>
      <dc:creator>SROLE1</dc:creator>
      <dc:date>2020-11-13T11:46:48Z</dc:date>
    </item>
    <item>
      <title>Re: Merge services using API, rules doesn't work</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118858#M2029</link>
      <description>&lt;P&gt;Thanks for your help,&lt;/P&gt;&lt;P&gt;Actual problem is, someone already created the rule to change the contextroot from it's original value. So rule created is not matching the value provided for contextroot, as the original value is something else.&lt;/P&gt;&lt;P&gt;I have increased the order and updated the original contextroot value and it did worked.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2020 08:50:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-API/Merge-services-using-API-rules-doesn-t-work/m-p/118858#M2029</guid>
      <dc:creator>SROLE1</dc:creator>
      <dc:date>2020-11-17T08:50:09Z</dc:date>
    </item>
  </channel>
</rss>

