<?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: splunk tags.conf disable stanza in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/splunk-tags-conf-disable-stanza/m-p/480619#M193024</link>
    <description>&lt;P&gt;but in as per your suggestion, the hard-work of eventtypes will be done by Splunk ? &lt;BR /&gt;
So in above example, the &lt;CODE&gt;[sshd_authentication]&lt;/CODE&gt; is done on EVERY single source-type and dataset, which is hugely inefficient &amp;amp; un-necessary step as we are not using the eventtype anymore. &lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2019 20:45:47 GMT</pubDate>
    <dc:creator>koshyk</dc:creator>
    <dc:date>2019-09-13T20:45:47Z</dc:date>
    <item>
      <title>splunk tags.conf disable stanza</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-tags-conf-disable-stanza/m-p/480617#M193022</link>
      <description>&lt;P&gt;We need to override a tags &amp;amp; eventtypes from one of the official TA  (eg &lt;CODE&gt;eventtype=ssh_authentication&lt;/CODE&gt;). &lt;/P&gt;

&lt;P&gt;eventtypes.conf have &lt;CODE&gt;disabled=true&lt;/CODE&gt; at a stanza level, but tags.conf does NOT have such ability as per spec.&lt;/P&gt;

&lt;P&gt;Any chance to disable entire stanza of tags.conf?&lt;/P&gt;

&lt;P&gt;What we are looking for is something like below in tags.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[eventtype=ssh_authentication]
disabled=true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;PS: If we don't do this, there is a "WARN" while doing Splunk search in GUI saying "unable to find eventtype=xxxxx". &lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2019 09:07:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-tags-conf-disable-stanza/m-p/480617#M193022</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2019-09-13T09:07:38Z</dc:date>
    </item>
    <item>
      <title>Re: splunk tags.conf disable stanza</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-tags-conf-disable-stanza/m-p/480618#M193023</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;If I understand your question correctly then you want to disable tags based on eventtypes &amp;amp; you are talking about below eventtypes.conf stanza&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sshd_authentication]
# osx sshd authentication error
# Jul 16 11:10:45 mycomputer sshd[34666]: error: PAM: authentication error for xxx from localhost via ::1
search = (NOT sourcetype=stash) NOT sourcetype=ossec sshd (((Accepted OR Failed OR failure OR "Invalid user" OR "authentication error") from) OR "Authorized to" OR "Authentication tried" OR "Login restricted")
#tags = authentication remote
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If this is the case then do not disable this stanza in eventtypes.conf but disable tags in tags.conf&lt;BR /&gt;
So if you want to disable &lt;CODE&gt;authentication&lt;/CODE&gt; tag then you can do below configuration in tags.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[eventtype=sshd_authentication]
authentication = disabled
remote = enabled
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 13 Sep 2019 11:20:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-tags-conf-disable-stanza/m-p/480618#M193023</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2019-09-13T11:20:01Z</dc:date>
    </item>
    <item>
      <title>Re: splunk tags.conf disable stanza</title>
      <link>https://community.splunk.com/t5/Splunk-Search/splunk-tags-conf-disable-stanza/m-p/480619#M193024</link>
      <description>&lt;P&gt;but in as per your suggestion, the hard-work of eventtypes will be done by Splunk ? &lt;BR /&gt;
So in above example, the &lt;CODE&gt;[sshd_authentication]&lt;/CODE&gt; is done on EVERY single source-type and dataset, which is hugely inefficient &amp;amp; un-necessary step as we are not using the eventtype anymore. &lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2019 20:45:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/splunk-tags-conf-disable-stanza/m-p/480619#M193024</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2019-09-13T20:45:47Z</dc:date>
    </item>
  </channel>
</rss>

