<?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: Slice Messages Before Search Time in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694147#M115353</link>
    <description>&lt;P&gt;1. Haven't we discussed it on Slack yesterday? (or was I discussing that with another person? The sourcetype was the same and the case was similar)&lt;/P&gt;&lt;P&gt;2. Your LINE_BREAKER should get rid of the "event": part already (it's within the capture group so it should be treated as line breaker and stripped).&lt;/P&gt;&lt;P&gt;So apparently your settings are not applied at all. I'd say you probably have your props set on a wrong component.&lt;/P&gt;</description>
    <pubDate>Wed, 24 Jul 2024 07:38:25 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2024-07-24T07:38:25Z</dc:date>
    <item>
      <title>Slice Messages Before Search Time</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694041#M115333</link>
      <description>&lt;P&gt;How can I cut some parts of my message prior to index time?&lt;BR /&gt;I tried to use both SEDCMD and transform on raw messages but I still get the full content each time.&lt;/P&gt;&lt;P&gt;Here is my current props configuration:&lt;/P&gt;&lt;P&gt;[ETW_SILK_JSON]&lt;BR /&gt;description = silk etw&lt;BR /&gt;LINE_BREAKER = ([\r\n]+"event":)&lt;BR /&gt;SHOULD_LINEMERGE = false&lt;BR /&gt;CHARSET = UTF-8&lt;BR /&gt;TRUNCATE = 0&lt;BR /&gt;# TRANSFORMS-cleanjson = strip_event_prefix&lt;BR /&gt;SEDCMD-strip_event = s/^"event":\{\s*//&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;And my message sample:&lt;BR /&gt;"event":{{"ProviderGuid":"7dd42a49-5329-4832-8dfd-43d979153a88","YaraMatch":[],"ProviderName":"Microsoft-Windows-Kernel-Network","EventName":"KERNEL_NETWORK_TASK_TCPIP/Datareceived.","Opcode":11,"OpcodeName":"Datareceived.","TimeStamp":"2024-07-22T14:29:27.6882177+03:00","ThreadID":10008,"ProcessID":1224,"ProcessName":"svchost","PointerSize":8,"EventDataLength":28,"XmlEventData":{"FormattedMessage":"TCPv4: 43 bytes received from 1,721,149,632:15,629 to -23,680,832:14,326. ","connid":"0","sport":"15,629","_PID":"820","seqnum":"0","MSec":"339.9806","saddr":"1,721,149,632","size":"43","PID":"1224","dport":"14,326","TID":"10008","ProviderName":"Microsoft-Windows-Kernel-Network","PName":"","EventName":"KERNEL_NETWORK_TASK_TCPIP/Datareceived.","daddr":"-23,680,832"}}}&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I want to get rid of the "event" prefix but none of the optios seems to work.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2024 09:01:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694041#M115333</guid>
      <dc:creator>DoubleAka</dc:creator>
      <dc:date>2024-07-23T09:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: Slice Messages Before Search Time</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694130#M115351</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/270192"&gt;@DoubleAka&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;your message seems to be in json, so if you delete part of the message (for example the first part) you lose the formatting and you can no longer use field extraction tools such as INDEXED_EXTRACTIONS or spath, furthermore you save very little by deleting just one word.&lt;BR /&gt;In any case, the SED_CMD command uses a substitution regex and the one you used is wrong because quotes must be escaped and you missed the global parameter:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;SEDCMD-strip_event = s/^\"event\":\{\s*//g&lt;/LI-CODE&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2024 06:14:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694130#M115351</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-07-24T06:14:12Z</dc:date>
    </item>
    <item>
      <title>Re: Slice Messages Before Search Time</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694147#M115353</link>
      <description>&lt;P&gt;1. Haven't we discussed it on Slack yesterday? (or was I discussing that with another person? The sourcetype was the same and the case was similar)&lt;/P&gt;&lt;P&gt;2. Your LINE_BREAKER should get rid of the "event": part already (it's within the capture group so it should be treated as line breaker and stripped).&lt;/P&gt;&lt;P&gt;So apparently your settings are not applied at all. I'd say you probably have your props set on a wrong component.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2024 07:38:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694147#M115353</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-07-24T07:38:25Z</dc:date>
    </item>
    <item>
      <title>Re: Slice Messages Before Search Time</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694296#M115366</link>
      <description>&lt;P&gt;Yes that is me, I am sorry for the using two channels for the same question, after asking in the Slack I searched again about the issue on the web but could not find any previous questions. Therefore I realized it could be better to ask here for future Splunk explorer. However eventually I was able to resolve the issue by editing my third party source code (not my Splunk UF) to produce valid formatted JSON messages. So problem is solved but not in conventional ways. For this reason I this think the question should be completely deleted in order to avoid future confusion.&lt;/P&gt;&lt;P&gt;How can I remove this question completely?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jul 2024 14:56:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694296#M115366</guid>
      <dc:creator>DoubleAka</dc:creator>
      <dc:date>2024-07-25T14:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Slice Messages Before Search Time</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694299#M115367</link>
      <description>&lt;P&gt;Well, that's a very good news &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; And IMHO it's a good solution to be found in the future - get your data in order first &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Just leave the thread be.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jul 2024 15:02:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Slice-Messages-Before-Search-Time/m-p/694299#M115367</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-07-25T15:02:51Z</dc:date>
    </item>
  </channel>
</rss>

