<?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: How to create custom error rule using request attribute value from API in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/177131#M2705</link>
    <description>&lt;P&gt;This is what support gave us:&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/service-api/failure-detection/" target="_blank"&gt;https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/service-api/failure-detection/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Dec 2021 13:49:51 GMT</pubDate>
    <dc:creator>ChadTurner</dc:creator>
    <dc:date>2021-12-08T13:49:51Z</dc:date>
    <item>
      <title>How to create custom error rule using request attribute value from API</title>
      <link>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/176485#M2682</link>
      <description>&lt;P&gt;We have 200 error codes captured in a request attribute. In which some are considered Technical errors and some are businesses errors. We need to create&amp;nbsp;custom error rules for all the technical errors (at least 100 codes) in 10 services =1000 custom error rules.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there any way we can use API for this or Reduce the effort by applying error detection rules for all 10 services at once?&lt;/P&gt;</description>
      <pubDate>Wed, 31 Aug 2022 10:46:07 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/176485#M2682</guid>
      <dc:creator>pavan_babu1</dc:creator>
      <dc:date>2022-08-31T10:46:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to create custom error rule using request attribute value from API</title>
      <link>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/177075#M2703</link>
      <description>&lt;P&gt;Thats a really good question. If you can use the API you might still end up hitting a limitation where you need to provide the entity ID, but granted that would cut down the workload.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can create a global rule as well:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ChadTurner_0-1638930705160.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/3677i0BD72A4C07DF9B4D/image-size/large?v=v2&amp;amp;px=999" role="button" title="ChadTurner_0-1638930705160.png" alt="ChadTurner_0-1638930705160.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ill see if Dynatrace is aware of a way to leverage the API for this&lt;/P&gt;</description>
      <pubDate>Wed, 08 Dec 2021 02:42:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/177075#M2703</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2021-12-08T02:42:53Z</dc:date>
    </item>
    <item>
      <title>Re: How to create custom error rule using request attribute value from API</title>
      <link>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/177131#M2705</link>
      <description>&lt;P&gt;This is what support gave us:&amp;nbsp;&lt;A href="https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/service-api/failure-detection/" target="_blank"&gt;https://www.dynatrace.com/support/help/dynatrace-api/configuration-api/service-api/failure-detection/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Dec 2021 13:49:51 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/177131#M2705</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2021-12-08T13:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to create custom error rule using request attribute value from API</title>
      <link>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/193882#M3166</link>
      <description>&lt;P&gt;Dear Chad,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I reopen a discussion here because I have the same need now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you know if its feasible globally or via API?&lt;BR /&gt;&lt;BR /&gt;Because making this service by service is a very big pain.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Sep 2022 06:16:08 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/193882#M3166</guid>
      <dc:creator>Malaik</dc:creator>
      <dc:date>2022-09-06T06:16:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to create custom error rule using request attribute value from API</title>
      <link>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/193887#M3167</link>
      <description>&lt;P&gt;You could create a script that will capture all the Service IDs, then once captured, you could add to that script to set the detection settings as desired on the number of services you are targeting. Then Post it to the API via the script, either with Postman or a tool similar.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Sep 2022 12:14:50 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/How-to-create-custom-error-rule-using-request-attribute-value/m-p/193887#M3167</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2022-09-05T12:14:50Z</dc:date>
    </item>
  </channel>
</rss>

