<?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: Search to find hosts sending syslog AND splunkd traffic in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Search-to-find-hosts-sending-syslog-AND-splunkd-traffic/m-p/9889#M53</link>
    <description>&lt;P&gt;what about this?&lt;/P&gt;

&lt;P&gt;[search sourcetype=splunkd | dedup host | fields + host] sourcetype=syslog&lt;/P&gt;

&lt;P&gt;subqueries hosts that are generating splunkd events, then use these hostnames to search for syslog sourcetypes.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Apr 2010 23:41:14 GMT</pubDate>
    <dc:creator>rayfoo</dc:creator>
    <dc:date>2010-04-05T23:41:14Z</dc:date>
    <item>
      <title>Search to find hosts sending syslog AND splunkd traffic</title>
      <link>https://community.splunk.com/t5/Installation/Search-to-find-hosts-sending-syslog-AND-splunkd-traffic/m-p/9887#M51</link>
      <description>&lt;P&gt;Any idea how to create a search that finds hosts that are sending BOTH syslog and splunkd traffic?  We'd like to turn off syslog for these hosts.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Feb 2010 06:00:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Search-to-find-hosts-sending-syslog-AND-splunkd-traffic/m-p/9887#M51</guid>
      <dc:creator>oreoshake</dc:creator>
      <dc:date>2010-02-25T06:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: Search to find hosts sending syslog AND splunkd traffic</title>
      <link>https://community.splunk.com/t5/Installation/Search-to-find-hosts-sending-syslog-AND-splunkd-traffic/m-p/9888#M52</link>
      <description>&lt;P&gt;What always springs to &lt;EM&gt;my&lt;/EM&gt; mind for this kind of goal is:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;run a search that gives the list of hosts sending syslog&lt;/LI&gt;
&lt;LI&gt;run a search that gives the list of hosts sendind splunkd&lt;/LI&gt;
&lt;LI&gt;compare the two lists&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;3 is a bit clumsy.  You can do it with the set command, but it is the clumsy part.&lt;/P&gt;

&lt;P&gt;The Search &amp;amp; Indexing team is much more fond of a declarative sql-like style, and may have a more clever variation.&lt;/P&gt;

&lt;P&gt;There's always the simplistic approach:&lt;/P&gt;

&lt;P&gt;For the last 24 hours:&lt;/P&gt;

&lt;P&gt;sourcetype=splunkd OR sourcetype=syslog | dedup host, sourcetype&lt;/P&gt;

&lt;P&gt;Then review the data manually&lt;/P&gt;

&lt;P&gt;If you wanted to get very fancy you could filter with something like:&lt;/P&gt;

&lt;P&gt;sourcetype=splunkd OR sourcetype=syslog | dedup host, sourcetype | transaction host | search linecount=2&lt;/P&gt;</description>
      <pubDate>Thu, 11 Mar 2010 16:53:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Search-to-find-hosts-sending-syslog-AND-splunkd-traffic/m-p/9888#M52</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-03-11T16:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: Search to find hosts sending syslog AND splunkd traffic</title>
      <link>https://community.splunk.com/t5/Installation/Search-to-find-hosts-sending-syslog-AND-splunkd-traffic/m-p/9889#M53</link>
      <description>&lt;P&gt;what about this?&lt;/P&gt;

&lt;P&gt;[search sourcetype=splunkd | dedup host | fields + host] sourcetype=syslog&lt;/P&gt;

&lt;P&gt;subqueries hosts that are generating splunkd events, then use these hostnames to search for syslog sourcetypes.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Apr 2010 23:41:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Search-to-find-hosts-sending-syslog-AND-splunkd-traffic/m-p/9889#M53</guid>
      <dc:creator>rayfoo</dc:creator>
      <dc:date>2010-04-05T23:41:14Z</dc:date>
    </item>
  </channel>
</rss>

