<?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: Count matching values on seperated fields in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344094#M101937</link>
    <description>&lt;P&gt;The simplest solution is to do a count by the fields you are interested in. It might still be very cluttered I guess, I assume SRC_PORT will vary a lot?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype="firewall" action=blocked | stats count by host src dest src_port dest_port
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 01 Aug 2017 08:13:25 GMT</pubDate>
    <dc:creator>knielsen</dc:creator>
    <dc:date>2017-08-01T08:13:25Z</dc:date>
    <item>
      <title>Count matching values on seperated fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344093#M101936</link>
      <description>&lt;P&gt;Hi there,&lt;BR /&gt;
i try to buildup a firewall report:&lt;/P&gt;

&lt;P&gt;"sourcetype="firewall"  action=blocked | table host src dest src_port dest_port"&lt;/P&gt;

&lt;P&gt;this gives me endless rows, and many of them are dublicated.&lt;BR /&gt;
i try to delete all the dublicates and count them so that i have something like&lt;/P&gt;

&lt;P&gt;HOST | SRC | DEST | SRC_PORT | DEST_PORT  | COUNT&lt;/P&gt;

&lt;P&gt;that would give a nice overview.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:10:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344093#M101936</guid>
      <dc:creator>Aufex</dc:creator>
      <dc:date>2020-09-29T15:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: Count matching values on seperated fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344094#M101937</link>
      <description>&lt;P&gt;The simplest solution is to do a count by the fields you are interested in. It might still be very cluttered I guess, I assume SRC_PORT will vary a lot?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype="firewall" action=blocked | stats count by host src dest src_port dest_port
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 01 Aug 2017 08:13:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344094#M101937</guid>
      <dc:creator>knielsen</dc:creator>
      <dc:date>2017-08-01T08:13:25Z</dc:date>
    </item>
    <item>
      <title>Re: Count matching values on seperated fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344095#M101938</link>
      <description>&lt;P&gt;thank you. yes ports change a lot. i think its much smarter to display the zones &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2017 08:17:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344095#M101938</guid>
      <dc:creator>Aufex</dc:creator>
      <dc:date>2017-08-01T08:17:39Z</dc:date>
    </item>
    <item>
      <title>Re: Count matching values on seperated fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344096#M101939</link>
      <description>&lt;P&gt;Don't forget to click &lt;CODE&gt;Accept&lt;/CODE&gt; to close the question.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2017 03:13:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Count-matching-values-on-seperated-fields/m-p/344096#M101939</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-08-02T03:13:57Z</dc:date>
    </item>
  </channel>
</rss>

