<?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 Solution : index renaming not working  when using _TCP_ROUTING in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Solution-index-renaming-not-working-when-using-TCP-ROUTING/m-p/704279#M116476</link>
    <description>&lt;P&gt;Hello, if you are using _TCP_ROUTING and index rename on target platform, logs may go to "last chance index"&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 13 Nov 2024 13:09:21 GMT</pubDate>
    <dc:creator>splunkreal</dc:creator>
    <dc:date>2024-11-13T13:09:21Z</dc:date>
    <item>
      <title>Solution : index renaming not working  when using _TCP_ROUTING</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Solution-index-renaming-not-working-when-using-TCP-ROUTING/m-p/704279#M116476</link>
      <description>&lt;P&gt;Hello, if you are using _TCP_ROUTING and index rename on target platform, logs may go to "last chance index"&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 13:09:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Solution-index-renaming-not-working-when-using-TCP-ROUTING/m-p/704279#M116476</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2024-11-13T13:09:21Z</dc:date>
    </item>
    <item>
      <title>Re: Solution : index renaming not working  when using _TCP_ROUTING</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Solution-index-renaming-not-working-when-using-TCP-ROUTING/m-p/704280#M116477</link>
      <description>&lt;P&gt;In this case review inputs.conf sourcetype and change it if you use default pretrained :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.3.0/Data/Listofpretrainedsourcetypes" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/9.3.0/Data/Listofpretrainedsourcetypes&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;"The source types marked with an asterisk ( * ) use the&amp;nbsp;INDEXED_EXTRACTIONS&amp;nbsp;attribute, which sets other attributes in props.conf to specific defaults and requires special handling to forward to another Splunk platform instance. See&amp;nbsp;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Extractfieldsfromfileswithstructureddata#Forward_fields_extracted_from_structured_data_files" target="_blank" rel="noopener"&gt;Forward fields extracted from structured data files&lt;/A&gt;."&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 13:10:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Solution-index-renaming-not-working-when-using-TCP-ROUTING/m-p/704280#M116477</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2024-11-13T13:10:44Z</dc:date>
    </item>
  </channel>
</rss>

