<?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 Finding Anomalies or Outliers in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659753#M227774</link>
    <description>&lt;P&gt;Trying to find anomalies for events. I have multiple services and multiple customers. I have an error "bucket" that is caputuring events for failures, exceeded, notified, etc.&lt;BR /&gt;I'm looking for a way to identify when there are anomalies or outliers for each of the services/customers. I have combined (eval) service, customer, and the error and just counting the number of error events generated by each service/customer.&lt;BR /&gt;So for example:&lt;BR /&gt;svcA&lt;BR /&gt;svcB&lt;BR /&gt;svcC&lt;BR /&gt;custA&lt;BR /&gt;custB&lt;BR /&gt;custC&lt;/P&gt;&lt;P&gt;would give&lt;BR /&gt;svcA-custA-failures 10&lt;BR /&gt;svcA-custA-exceeded 5&lt;BR /&gt;svcA-custA-notified 25&lt;BR /&gt;svcB-custA-failures 11&lt;BR /&gt;svcB-custA-exceeded 9&lt;BR /&gt;svcB-custA-notified 33&lt;BR /&gt;svcB-custB-failures 3&lt;BR /&gt;svcA-custB-exceeded 7&lt;BR /&gt;svcA-custB-notified 22&lt;BR /&gt;svcA-custC-exceeded 8&lt;BR /&gt;svcA-custC-failures 3&lt;BR /&gt;svcA-custC-notified 267&lt;BR /&gt;svcC-custC-exceeded 1&lt;BR /&gt;svcC-custC-failures 4&lt;BR /&gt;svcC-custB-notified 145&lt;BR /&gt;svcC-custA-notified 17&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Something along the lines of this:&lt;BR /&gt;&lt;BR /&gt;| eval Svc-Cust-Evnt=Svc."-".Cust."-".Evnt&lt;BR /&gt;| stats sum(error) by Svc-Cust-Evnt&lt;BR /&gt;| rename sum(error) as count&lt;BR /&gt;| sort -count&lt;/P&gt;</description>
    <pubDate>Thu, 05 Oct 2023 07:29:19 GMT</pubDate>
    <dc:creator>irkey</dc:creator>
    <dc:date>2023-10-05T07:29:19Z</dc:date>
    <item>
      <title>Finding Anomalies or Outliers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659753#M227774</link>
      <description>&lt;P&gt;Trying to find anomalies for events. I have multiple services and multiple customers. I have an error "bucket" that is caputuring events for failures, exceeded, notified, etc.&lt;BR /&gt;I'm looking for a way to identify when there are anomalies or outliers for each of the services/customers. I have combined (eval) service, customer, and the error and just counting the number of error events generated by each service/customer.&lt;BR /&gt;So for example:&lt;BR /&gt;svcA&lt;BR /&gt;svcB&lt;BR /&gt;svcC&lt;BR /&gt;custA&lt;BR /&gt;custB&lt;BR /&gt;custC&lt;/P&gt;&lt;P&gt;would give&lt;BR /&gt;svcA-custA-failures 10&lt;BR /&gt;svcA-custA-exceeded 5&lt;BR /&gt;svcA-custA-notified 25&lt;BR /&gt;svcB-custA-failures 11&lt;BR /&gt;svcB-custA-exceeded 9&lt;BR /&gt;svcB-custA-notified 33&lt;BR /&gt;svcB-custB-failures 3&lt;BR /&gt;svcA-custB-exceeded 7&lt;BR /&gt;svcA-custB-notified 22&lt;BR /&gt;svcA-custC-exceeded 8&lt;BR /&gt;svcA-custC-failures 3&lt;BR /&gt;svcA-custC-notified 267&lt;BR /&gt;svcC-custC-exceeded 1&lt;BR /&gt;svcC-custC-failures 4&lt;BR /&gt;svcC-custB-notified 145&lt;BR /&gt;svcC-custA-notified 17&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Something along the lines of this:&lt;BR /&gt;&lt;BR /&gt;| eval Svc-Cust-Evnt=Svc."-".Cust."-".Evnt&lt;BR /&gt;| stats sum(error) by Svc-Cust-Evnt&lt;BR /&gt;| rename sum(error) as count&lt;BR /&gt;| sort -count&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 07:29:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659753#M227774</guid>
      <dc:creator>irkey</dc:creator>
      <dc:date>2023-10-05T07:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: Finding Anomalies or Outliers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659757#M227775</link>
      <description>&lt;P&gt;It is not clear what your criteria are for determining what an anomaly is.&lt;/P&gt;&lt;P&gt;Also, from your example, you don't need to combine the fields, you could just to something like this&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| stats sum(error) as count by Svc Cust Evnt
| sort -count&lt;/LI-CODE&gt;</description>
      <pubDate>Thu, 05 Oct 2023 08:38:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659757#M227775</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2023-10-05T08:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: Finding Anomalies or Outliers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659813#M227792</link>
      <description>&lt;P&gt;Each service/customer has different usage patterns...some are "normally" less busy than others. So I thought there is a way to identity when something does not follow the "normal" pattern witout putting in static thresholds?&amp;nbsp;So for the service/customer that is normally slower the threshold will be less than a busier service/customer.&amp;nbsp;If svcA-custA normally has 2000 events a day and svcA-custB has only 100 events a day the thresholds will be different.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 15:43:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659813#M227792</guid>
      <dc:creator>irkey</dc:creator>
      <dc:date>2023-10-05T15:43:02Z</dc:date>
    </item>
    <item>
      <title>Re: Finding Anomalies or Outliers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659815#M227793</link>
      <description>&lt;P&gt;Sounds like you need some sort of baseline for each service/customer - I would suggest you store this in a summary index. You can then retrieve the relevant stat from the summary index and compare it to you current actual to determine if it is anomalous.&lt;/P&gt;&lt;P&gt;You could also look at the MLTK, however, for this sort of analysis, you may end up with multiple models for each service/customer combination, which becomes quite unwieldy.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 15:52:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659815#M227793</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2023-10-05T15:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: Finding Anomalies or Outliers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659816#M227794</link>
      <description>&lt;P&gt;Interesting. Can you provide a run anywhere query example of how I would do the comparison?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 15:57:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Finding-Anomalies-or-Outliers/m-p/659816#M227794</guid>
      <dc:creator>irkey</dc:creator>
      <dc:date>2023-10-05T15:57:00Z</dc:date>
    </item>
  </channel>
</rss>

