<?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: Most common events/issues/words in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424986#M121865</link>
    <description>&lt;P&gt;Hi Skalli. You might want to have a play around with the these two apps.&lt;/P&gt;

&lt;P&gt;NLP Text Analytics - &lt;A href="https://splunkbase.splunk.com/app/4066/"&gt;https://splunkbase.splunk.com/app/4066/&lt;/A&gt; - A collection of bits a pieces to do text analysis based around NLTK3.3 and Splunk's MLTK.&lt;/P&gt;

&lt;P&gt;NLP Natural Language Toolkit - NLTK wrapper - &lt;A href="https://splunkbase.splunk.com/app/4057/"&gt;https://splunkbase.splunk.com/app/4057/&lt;/A&gt; - Another wrapper for some of the same python libraries for Natural Language Processing.&lt;/P&gt;

&lt;P&gt;Should be able to get the job done, not sure how well at large scale but 11k records is not much.&lt;/P&gt;</description>
    <pubDate>Tue, 06 Aug 2019 16:15:52 GMT</pubDate>
    <dc:creator>warwicks</dc:creator>
    <dc:date>2019-08-06T16:15:52Z</dc:date>
    <item>
      <title>Most common events/issues/words</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424982#M121861</link>
      <description>&lt;P&gt;Hello guys, &lt;/P&gt;

&lt;P&gt;I'm new in SPLUNK. Just wanted to ask for an advice :). Currently, I have 11,000 ticket data and I'm trying to filter the most common events/issues/words on it. I am trying the use of cluster, regex and lookup. &lt;/P&gt;

&lt;P&gt;What do you think is the best approach for this? &lt;/P&gt;

&lt;P&gt;Thank you in advance everyone. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 07:14:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424982#M121861</guid>
      <dc:creator>chinkeeparco</dc:creator>
      <dc:date>2019-08-02T07:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: Most common events/issues/words</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424983#M121862</link>
      <description>&lt;P&gt;Hey and welcome to the Splunk community. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;First of all, the answers to your questions have a "depends" in it. If your data is in an easy structure to onboard, you might want to start reading and working through the docs: &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Data/Getstartedwithgettingdatain"&gt;getting data in&lt;/A&gt;. After the data is onboarded correctly, the next thing would be to build field extractions based on the events. For this, you can use the &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Knowledge/ExtractfieldsinteractivelywithIFX"&gt;field extractor&lt;/A&gt;. After you have built your fields, you can easily filter on those with something more simple like &lt;CODE&gt;index=yourIndex sourcetype=yourSourcetype |top your_desired_field1, field2 ...&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;Skalli&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 08:28:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424983#M121862</guid>
      <dc:creator>skalliger</dc:creator>
      <dc:date>2019-08-02T08:28:43Z</dc:date>
    </item>
    <item>
      <title>Re: Most common events/issues/words</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424984#M121863</link>
      <description>&lt;P&gt;Hi Skalli! thank you for your answer. It was not a simple unfortunately.. &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt; I'll give a sample data below:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Sample Data&lt;/STRONG&gt;&lt;BR /&gt;
Can you please reset my password? &lt;BR /&gt;
Password Reset request&lt;BR /&gt;
Unable to open my account&lt;BR /&gt;
Please help! Can't access my account.&lt;BR /&gt;
Can't connect to Wifi&lt;BR /&gt;
Reset my Password&lt;BR /&gt;
... and so on.&lt;/P&gt;

&lt;P&gt;I wanted to automatically filter the 11,000 data on what is the most frequent words. thanks &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 08:39:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424984#M121863</guid>
      <dc:creator>chinkeeparco</dc:creator>
      <dc:date>2019-08-02T08:39:15Z</dc:date>
    </item>
    <item>
      <title>Re: Most common events/issues/words</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424985#M121864</link>
      <description>&lt;P&gt;There really is no good way to do this that will scale to any degree.  You should consider another Big Data tool that would be more appropriate.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Aug 2019 15:45:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424985#M121864</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-08-06T15:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: Most common events/issues/words</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424986#M121865</link>
      <description>&lt;P&gt;Hi Skalli. You might want to have a play around with the these two apps.&lt;/P&gt;

&lt;P&gt;NLP Text Analytics - &lt;A href="https://splunkbase.splunk.com/app/4066/"&gt;https://splunkbase.splunk.com/app/4066/&lt;/A&gt; - A collection of bits a pieces to do text analysis based around NLTK3.3 and Splunk's MLTK.&lt;/P&gt;

&lt;P&gt;NLP Natural Language Toolkit - NLTK wrapper - &lt;A href="https://splunkbase.splunk.com/app/4057/"&gt;https://splunkbase.splunk.com/app/4057/&lt;/A&gt; - Another wrapper for some of the same python libraries for Natural Language Processing.&lt;/P&gt;

&lt;P&gt;Should be able to get the job done, not sure how well at large scale but 11k records is not much.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Aug 2019 16:15:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424986#M121865</guid>
      <dc:creator>warwicks</dc:creator>
      <dc:date>2019-08-06T16:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: Most common events/issues/words</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424987#M121866</link>
      <description>&lt;P&gt;I wasn't the one asking but this is actually a great answer. I've linked the NLP once myself but even didn't think about it in this case. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Skalli&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2019 08:44:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Most-common-events-issues-words/m-p/424987#M121866</guid>
      <dc:creator>skalliger</dc:creator>
      <dc:date>2019-08-07T08:44:06Z</dc:date>
    </item>
  </channel>
</rss>

