<?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 Avoid alerts limit for SLO: metric-selector-based configurations max 100 in Automations</title>
    <link>https://community.dynatrace.com/t5/Automations/Avoid-alerts-limit-for-SLO-metric-selector-based-configurations/m-p/219519#M1087</link>
    <description>&lt;P&gt;SLO created pseudo-metrics which not possible to use in Metric key configuration.&lt;BR /&gt;(Err: Stored metric expressions are only supported in metric-selector-based query mode.)&lt;/P&gt;
&lt;P&gt;This leads to affective limit about 100 SLO or less:&lt;BR /&gt;Configuration limit of metric-selector-based configurations:&lt;BR /&gt;Static threshold: 4 out of 100&lt;BR /&gt;Auto adaptive threshold: 0 out of 100&lt;BR /&gt;Seasonal baseline: 1 out of 100&lt;BR /&gt;&lt;BR /&gt;We want to have SLO for each key user action and different API.&lt;BR /&gt;In this case it is just impossible.&lt;/P&gt;
&lt;P&gt;Based on standard best practices SLO should not be without the alert.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;What is workaround?&lt;/P&gt;</description>
    <pubDate>Thu, 03 Aug 2023 09:30:09 GMT</pubDate>
    <dc:creator>Slawa</dc:creator>
    <dc:date>2023-08-03T09:30:09Z</dc:date>
    <item>
      <title>Avoid alerts limit for SLO: metric-selector-based configurations max 100</title>
      <link>https://community.dynatrace.com/t5/Automations/Avoid-alerts-limit-for-SLO-metric-selector-based-configurations/m-p/219519#M1087</link>
      <description>&lt;P&gt;SLO created pseudo-metrics which not possible to use in Metric key configuration.&lt;BR /&gt;(Err: Stored metric expressions are only supported in metric-selector-based query mode.)&lt;/P&gt;
&lt;P&gt;This leads to affective limit about 100 SLO or less:&lt;BR /&gt;Configuration limit of metric-selector-based configurations:&lt;BR /&gt;Static threshold: 4 out of 100&lt;BR /&gt;Auto adaptive threshold: 0 out of 100&lt;BR /&gt;Seasonal baseline: 1 out of 100&lt;BR /&gt;&lt;BR /&gt;We want to have SLO for each key user action and different API.&lt;BR /&gt;In this case it is just impossible.&lt;/P&gt;
&lt;P&gt;Based on standard best practices SLO should not be without the alert.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;What is workaround?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Aug 2023 09:30:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Avoid-alerts-limit-for-SLO-metric-selector-based-configurations/m-p/219519#M1087</guid>
      <dc:creator>Slawa</dc:creator>
      <dc:date>2023-08-03T09:30:09Z</dc:date>
    </item>
    <item>
      <title>Re: Avoid alerts limit for SLO: metric-selector-based configurations max 100</title>
      <link>https://community.dynatrace.com/t5/Automations/Avoid-alerts-limit-for-SLO-metric-selector-based-configurations/m-p/222763#M1089</link>
      <description>&lt;P&gt;I had a conversation with the support: limit can be increased to 500 by request for environment.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2023 06:37:23 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Avoid-alerts-limit-for-SLO-metric-selector-based-configurations/m-p/222763#M1089</guid>
      <dc:creator>Slawa</dc:creator>
      <dc:date>2023-09-12T06:37:23Z</dc:date>
    </item>
  </channel>
</rss>

