<?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 _audit index data retention in Splunk cluster in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/audit-index-data-retention-in-Splunk-cluster/m-p/468961#M80685</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a Splunk cluster that consists of:&lt;BR /&gt;
- 1 cluster master&lt;BR /&gt;
- 3 indexers&lt;BR /&gt;
- 1 search head&lt;/P&gt;

&lt;P&gt;The indexes at the search head are configured to be forwarded to the indexers.&lt;/P&gt;

&lt;P&gt;I would like to set a retention period shorter than the 6-year default to the _audit index in this Splunk cluster.&lt;/P&gt;

&lt;P&gt;Normally, to deploy indexes to the indexers, the procedure I use is to create an app with an indexes.conf inside the cluster master's master-apps directory, then push the configuration. However, I'm unsure if this procedure would work for _audit.&lt;/P&gt;

&lt;P&gt;How should I go about changing the retention period of the _audit index in all the indexers?&lt;/P&gt;</description>
    <pubDate>Sun, 22 Dec 2019 22:06:58 GMT</pubDate>
    <dc:creator>pcsegal1</dc:creator>
    <dc:date>2019-12-22T22:06:58Z</dc:date>
    <item>
      <title>_audit index data retention in Splunk cluster</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/audit-index-data-retention-in-Splunk-cluster/m-p/468961#M80685</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a Splunk cluster that consists of:&lt;BR /&gt;
- 1 cluster master&lt;BR /&gt;
- 3 indexers&lt;BR /&gt;
- 1 search head&lt;/P&gt;

&lt;P&gt;The indexes at the search head are configured to be forwarded to the indexers.&lt;/P&gt;

&lt;P&gt;I would like to set a retention period shorter than the 6-year default to the _audit index in this Splunk cluster.&lt;/P&gt;

&lt;P&gt;Normally, to deploy indexes to the indexers, the procedure I use is to create an app with an indexes.conf inside the cluster master's master-apps directory, then push the configuration. However, I'm unsure if this procedure would work for _audit.&lt;/P&gt;

&lt;P&gt;How should I go about changing the retention period of the _audit index in all the indexers?&lt;/P&gt;</description>
      <pubDate>Sun, 22 Dec 2019 22:06:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/audit-index-data-retention-in-Splunk-cluster/m-p/468961#M80685</guid>
      <dc:creator>pcsegal1</dc:creator>
      <dc:date>2019-12-22T22:06:58Z</dc:date>
    </item>
    <item>
      <title>Re: _audit index data retention in Splunk cluster</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/audit-index-data-retention-in-Splunk-cluster/m-p/468962#M80686</link>
      <description>&lt;P&gt;HI @pcsegal1,&lt;BR /&gt;
for my experience, you could have two different approaches, both correct and efficient:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;you could have all the indexes in a dedicated TA (called e.g. &lt;CODE&gt;TA_Indexers&lt;/CODE&gt;) located in &lt;CODE&gt;%SPLUNK_HOME/etc/master-apps&lt;/CODE&gt;, that contains indexes.conf and eventually props.conf and transforms.conf of all your apps , then put in &lt;CODE&gt;%SPLUNK_HOME/etc/master-apps/_cluster/local&lt;/CODE&gt; indexes.conf for internal indexes (as _audit); in this way you divide physically and concettually your configuration files on Indexers Cluster;&lt;/LI&gt;
&lt;LI&gt;in the above TA_Indexers, put all the conf files, both of internal and external indexes.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;I prefer the first one, but also the second is correct.&lt;/P&gt;

&lt;P&gt;In both cases, remember to add comments to each stanza.&lt;/P&gt;

&lt;P&gt;Also the _audit index and the other internal indexes can be managed in this way.&lt;/P&gt;

&lt;P&gt;Only one attention: choose the correct retention period related with your security policies and your regulation (e.g. in Italy audit logs must be archived at least for six months).&lt;/P&gt;

&lt;P&gt;Ciao and Merry Christmas.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 23 Dec 2019 08:05:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/audit-index-data-retention-in-Splunk-cluster/m-p/468962#M80686</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2019-12-23T08:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: _audit index data retention in Splunk cluster</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/audit-index-data-retention-in-Splunk-cluster/m-p/468963#M80687</link>
      <description>&lt;P&gt;I applied your first approach (put in &lt;CODE&gt;%SPLUNK_HOME/etc/master-apps/_cluster/local&lt;/CODE&gt; an &lt;CODE&gt;indexes.conf&lt;/CODE&gt; file for the &lt;CODE&gt;_audit&lt;/CODE&gt; index) and it worked as expected. Thank you and Merry Christmas.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Dec 2019 21:31:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/audit-index-data-retention-in-Splunk-cluster/m-p/468963#M80687</guid>
      <dc:creator>pcsegal1</dc:creator>
      <dc:date>2019-12-23T21:31:38Z</dc:date>
    </item>
  </channel>
</rss>

