<?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: Corrupted fields problem in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470427#M192143</link>
    <description>&lt;P&gt;Especially my purpose is trying to fix irrelevant values on my search results at field 7 side.&lt;BR /&gt;
I've attached 2 screen shots for clarification. &lt;BR /&gt;
&lt;IMG src="https://i.stack.imgur.com/YYAZg.png" alt="alt text" /&gt;&lt;/P&gt;

&lt;P&gt;&lt;IMG src="https://i.stack.imgur.com/MJEiT.jpg" alt="alt text" /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2020 12:55:50 GMT</pubDate>
    <dc:creator>dunyaelbasan</dc:creator>
    <dc:date>2020-06-03T12:55:50Z</dc:date>
    <item>
      <title>Corrupted fields problem</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470425#M192141</link>
      <description>&lt;P&gt;I have a problem on this search below for last 25 days:&lt;/P&gt;

&lt;P&gt;index=syslog Reason="Interface physical link is down" OR Reason="Interface physical link is up" NOT mainIfname="Vlanif*" "nw_ra_a98c_01.34_krtti"&lt;/P&gt;

&lt;P&gt;Normally field7 values are like these ones:&lt;/P&gt;

&lt;P&gt;Region  field7                                  Date    mainIfname                  Reason  count&lt;BR /&gt;
ASYA    nw_ra_m02f_01.34pndkdv  may 9   GigabitEthernet0/3/6    Interface physical link is up   3&lt;BR /&gt;
ASYA    nw_ra_m02f_01.34pldtwr  may 9   GigabitEthernet0/3/24   Interface physical link is up   2&lt;/P&gt;

&lt;P&gt;But recently they wee like this:&lt;/P&gt;

&lt;P&gt;00:00:00.599 nw_ra_a98c_01.34_krtti &lt;BR /&gt;
00:00:03.078 nw_ra_a98c_01.34_krtti &lt;/P&gt;

&lt;P&gt;I think problem may be related to:&lt;/P&gt;

&lt;P&gt;It started to happen after the disk free alarm. (-Cri- Swap reservation, bottleneck situation, current value: 95.00% exceeds configured threshold: 90.00%. : 07:17 17/02/20)&lt;BR /&gt;
Especially This is not about disk, it's about swap space, the application finishes memory and then goes to swap use. There was memory increase before, but obviously it was insufficient, it is switching to swap again.&lt;BR /&gt;
I need to understand: ''Why they use so many resources?''&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 05:36:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470425#M192141</guid>
      <dc:creator>dunyaelbasan</dc:creator>
      <dc:date>2020-09-30T05:36:41Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted fields problem</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470426#M192142</link>
      <description>&lt;P&gt;It's not clear what problem you're asking about.  Is the problem with a Splunk search, your Ethernet interfaces, disk space, swap space, or memory use?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 12:50:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470426#M192142</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-06-03T12:50:10Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted fields problem</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470427#M192143</link>
      <description>&lt;P&gt;Especially my purpose is trying to fix irrelevant values on my search results at field 7 side.&lt;BR /&gt;
I've attached 2 screen shots for clarification. &lt;BR /&gt;
&lt;IMG src="https://i.stack.imgur.com/YYAZg.png" alt="alt text" /&gt;&lt;/P&gt;

&lt;P&gt;&lt;IMG src="https://i.stack.imgur.com/MJEiT.jpg" alt="alt text" /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 12:55:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470427#M192143</guid>
      <dc:creator>dunyaelbasan</dc:creator>
      <dc:date>2020-06-03T12:55:50Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted fields problem</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470428#M192144</link>
      <description>&lt;P&gt;Please share some sample events (not just field7) and the props.conf settings for the sourcetype.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 14:58:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/470428#M192144</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-06-03T14:58:51Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted fields problem</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/503982#M192145</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I've attached the xample events, one from the normal situation, and one from the problematic situation.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://drive.google.com/drive/folders/1IaswXnbWTORN0ES0NzL0ceDAHr4iIyS6?usp=sharing" target="_blank"&gt;https://drive.google.com/drive/folders/1IaswXnbWTORN0ES0NzL0ceDAHr4iIyS6?usp=sharing&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;inside of props.conf:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TRANSFORMS-ddos_routing = ddos_routing&lt;/P&gt;&lt;P&gt;TRANSFORMS-ddos_sourcetype_cloud = ddos_cloud&lt;/P&gt;&lt;P&gt;TRANSFORMS-ddos_sourcetype_host = ddos_host&lt;/P&gt;&lt;P&gt;TRANSFORMS-ddos_sourcetype_tms = ddos_tms&lt;/P&gt;&lt;P&gt;TRANSFORMS-ddos_sourcetype_profiled = ddos_profiled&lt;/P&gt;&lt;P&gt;TRANSFORMS-access_routing = access_routing&lt;/P&gt;&lt;P&gt;TRANSFORMS-access_sourcetype_switch = access_switch&lt;/P&gt;&lt;P&gt;TRANSFORMS-access_sourcetype_gpon = access_gpon&lt;/P&gt;&lt;P&gt;TRANSFORMS-access_sourcetype_router = access_router&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 18:31:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Corrupted-fields-problem/m-p/503982#M192145</guid>
      <dc:creator>dunyaelbasan</dc:creator>
      <dc:date>2020-06-11T18:31:55Z</dc:date>
    </item>
  </channel>
</rss>

