<?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: Source attribute has to be a certain length? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Source-attribute-has-to-be-a-certain-length/m-p/747216#M118747</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/310548"&gt;@bgresty&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This behavior is almost certainly caused by ingestion-time processing rules configured in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;transforms.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;on the indexer(s) receiving data for Index 2.&lt;/P&gt;&lt;P&gt;Look for stanzas in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;that match the source type, host, or index of the data being sent to Index 2. These stanzas might contain&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;TRANSFORMS,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;FILTER, or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;ROUTEID&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;attributes that point to stanzas in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;transforms.conf.&lt;/P&gt;&lt;P&gt;In&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;transforms.conf, look for stanzas referenced by&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;that use&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;REGEX&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;FILTER&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to evaluate the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;source&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;field and then route events to a null queue (queue=nullQueue) or otherwise discard them. A regex or filter condition might be inadvertently matching sources shorter than 14 characters.&lt;/P&gt;&lt;P&gt;Compare the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;transforms.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;files on the indexers handling data for Index 1 and Index 2 to identify the difference.&lt;/P&gt;&lt;P&gt;You can use the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;splunk btool&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command to inspect the effective configuration:&lt;/P&gt;&lt;PRE&gt;splunk btool props list &amp;lt;your_sourcetype&amp;gt; --debug
splunk btool transforms list --debug&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This will show you which configuration files are contributing to the settings for your source type and transforms.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
    <pubDate>Thu, 29 May 2025 16:32:55 GMT</pubDate>
    <dc:creator>livehybrid</dc:creator>
    <dc:date>2025-05-29T16:32:55Z</dc:date>
    <item>
      <title>Source attribute has to be a certain length?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-attribute-has-to-be-a-certain-length/m-p/747215#M118746</link>
      <description>&lt;P&gt;Hi, we've encountered some unusual behaviour when ingesting data and are at a loss as to what might be causing it. We have two presumably identical indexes ingesting identically structured messages from different regions via an HEC for each.&lt;/P&gt;&lt;P&gt;Index 1 has no issue, all messages are ingested no problem.&lt;/P&gt;&lt;P&gt;On Index 2, events only appear if the source attribute of the message is equal or greater than 14 characters long.&lt;/P&gt;&lt;P&gt;e.g.:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp;other_data: ...&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;source&lt;/SPAN&gt;: &lt;SPAN class=""&gt;12345678901234&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;Any ideas?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 29 May 2025 15:59:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-attribute-has-to-be-a-certain-length/m-p/747215#M118746</guid>
      <dc:creator>bgresty</dc:creator>
      <dc:date>2025-05-29T15:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: Source attribute has to be a certain length?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-attribute-has-to-be-a-certain-length/m-p/747216#M118747</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/310548"&gt;@bgresty&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This behavior is almost certainly caused by ingestion-time processing rules configured in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;transforms.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;on the indexer(s) receiving data for Index 2.&lt;/P&gt;&lt;P&gt;Look for stanzas in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;that match the source type, host, or index of the data being sent to Index 2. These stanzas might contain&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;TRANSFORMS,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;FILTER, or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;ROUTEID&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;attributes that point to stanzas in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;transforms.conf.&lt;/P&gt;&lt;P&gt;In&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;transforms.conf, look for stanzas referenced by&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;that use&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;REGEX&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;FILTER&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to evaluate the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;source&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;field and then route events to a null queue (queue=nullQueue) or otherwise discard them. A regex or filter condition might be inadvertently matching sources shorter than 14 characters.&lt;/P&gt;&lt;P&gt;Compare the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;props.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;transforms.conf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;files on the indexers handling data for Index 1 and Index 2 to identify the difference.&lt;/P&gt;&lt;P&gt;You can use the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;splunk btool&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;command to inspect the effective configuration:&lt;/P&gt;&lt;PRE&gt;splunk btool props list &amp;lt;your_sourcetype&amp;gt; --debug
splunk btool transforms list --debug&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This will show you which configuration files are contributing to the settings for your source type and transforms.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2025 16:32:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-attribute-has-to-be-a-certain-length/m-p/747216#M118747</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2025-05-29T16:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: Source attribute has to be a certain length?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Source-attribute-has-to-be-a-certain-length/m-p/747248#M118748</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/310548"&gt;@bgresty&lt;/a&gt;&amp;nbsp;I strongly agree with what&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/170906"&gt;@livehybrid&lt;/a&gt;&amp;nbsp;says.&lt;BR /&gt;&lt;SPAN&gt;Your 14 characters highlight, pointing towards a configuration that's unintentionally filtering or misinterpreting data based on this field's length which should be in your props/transforms conf.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 30 May 2025 04:35:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Source-attribute-has-to-be-a-certain-length/m-p/747248#M118748</guid>
      <dc:creator>PrewinThomas</dc:creator>
      <dc:date>2025-05-30T04:35:29Z</dc:date>
    </item>
  </channel>
</rss>

