<?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 When to establish boundaries for MLTK based alerts? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/When-to-establish-boundaries-for-MLTK-based-alerts/m-p/603610#M77082</link>
    <description>&lt;P&gt;I was working in the MLTK, very new to it and exploring. I was working to establish a few searches where I will fit a algorithm and then apply it to identify if any values out of a set boundary and then alert on that. I have two question from this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this a valid use case or not so much?&lt;/P&gt;&lt;P&gt;I have a predicted value after my fit but, its too close to my actual values so I was thinking of doing something like(+ or - depending on need):&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;eval bound = (predictedavg - (stdev * 3))&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;Would it be more beneficial to calculate this in the fit search or when applying the model?&lt;/P&gt;</description>
    <pubDate>Tue, 28 Jun 2022 15:05:59 GMT</pubDate>
    <dc:creator>SMM10</dc:creator>
    <dc:date>2022-06-28T15:05:59Z</dc:date>
    <item>
      <title>When to establish boundaries for MLTK based alerts?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/When-to-establish-boundaries-for-MLTK-based-alerts/m-p/603610#M77082</link>
      <description>&lt;P&gt;I was working in the MLTK, very new to it and exploring. I was working to establish a few searches where I will fit a algorithm and then apply it to identify if any values out of a set boundary and then alert on that. I have two question from this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this a valid use case or not so much?&lt;/P&gt;&lt;P&gt;I have a predicted value after my fit but, its too close to my actual values so I was thinking of doing something like(+ or - depending on need):&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;eval bound = (predictedavg - (stdev * 3))&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;Would it be more beneficial to calculate this in the fit search or when applying the model?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 15:05:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/When-to-establish-boundaries-for-MLTK-based-alerts/m-p/603610#M77082</guid>
      <dc:creator>SMM10</dc:creator>
      <dc:date>2022-06-28T15:05:59Z</dc:date>
    </item>
  </channel>
</rss>

