<?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: Does Cribl always produce cooked data? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758719#M120286</link>
    <description>&lt;P&gt;If Cribl is sending to the HEC event endpoint then the data is treated as cooked by Splunk and index-time props will be skipped.&amp;nbsp; If the data is sent to the raw endpoint then it is uncooked and normal pipeline processing applies.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Feb 2026 18:52:59 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2026-02-24T18:52:59Z</dc:date>
    <item>
      <title>Does Cribl always produce cooked data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758708#M120284</link>
      <description>&lt;P&gt;I realize in the new system I take care of, that all the Windows wineventlogs are being streamed to Splunk via Cribl, and it seems that the data comes cooked.&lt;/P&gt;&lt;P&gt;Is data always "cooked" when passing through Cribl? Specifically, if the logs are coming from a Windows Universal Forwarder (UF) and passing through Cribl before hitting the Indexers, does Cribl inherently "cook" the data, or is this a configuration choice within the Cribl Pipeline?&lt;/P&gt;&lt;P&gt;How do I maintain control over field extractions? In a traditional setup, we rely heavily on the Splunk Add-on for Microsoft Windows (Windows TA) for index-time and search-time extractions. If the data is being transformed in Cribl, does that bypass the TA’s logic?&lt;/P&gt;</description>
      <pubDate>Tue, 24 Feb 2026 18:15:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758708#M120284</guid>
      <dc:creator>LovingSplunk</dc:creator>
      <dc:date>2026-02-24T18:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: Does Cribl always produce cooked data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758719#M120286</link>
      <description>&lt;P&gt;If Cribl is sending to the HEC event endpoint then the data is treated as cooked by Splunk and index-time props will be skipped.&amp;nbsp; If the data is sent to the raw endpoint then it is uncooked and normal pipeline processing applies.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Feb 2026 18:52:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758719#M120286</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2026-02-24T18:52:59Z</dc:date>
    </item>
    <item>
      <title>Re: Does Cribl always produce cooked data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758759#M120287</link>
      <description>&lt;P&gt;It depends. Cribl can handle outputting to Splunk in one of several ways.&lt;/P&gt;&lt;P&gt;It can do raw event to /services/collector/raw - this way the event is ingested as raw and goes through all normal event processing except line breaking IIRC&lt;/P&gt;&lt;P&gt;It can do HEC to /services/collector/event - this way the event goes directly into typingQueue (I'm not sure if you can tell Cribl to use the ?auto_extract_timestamp=true parameter to push the events earlier in the pipeline.&lt;/P&gt;&lt;P&gt;And it can do s2s (either directly or over HTTP via /services/collector/s2s) in which case it sends data as cooked and parsed (not just cooked!).&lt;/P&gt;&lt;P&gt;Anyway, it has nothing to do with search-time extractions. Search-time extractions happen - as the name says - during searching so it doesn't matter how the data was ingested (unless they rely on something that should have happened during indexing, like sourcetype rewrite).&lt;/P&gt;</description>
      <pubDate>Tue, 24 Feb 2026 21:01:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758759#M120287</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2026-02-24T21:01:23Z</dc:date>
    </item>
    <item>
      <title>Re: Does Cribl always produce cooked data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758826#M120291</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;, I'm completely new to Cribl, and I'm in charge of this system that utilizes it. How can I figure out how Cribl interacts with Splunk? most likely, directly to the indexers.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Feb 2026 15:38:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758826#M120291</guid>
      <dc:creator>LovingSplunk</dc:creator>
      <dc:date>2026-02-26T15:38:42Z</dc:date>
    </item>
    <item>
      <title>Re: Does Cribl always produce cooked data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758993#M120310</link>
      <description>&lt;P&gt;Do you mean that you want to check how your specific setup is configured? You have to check your pipelines or whatever they are called in Cribl (I don't remember; I don't use Cribl on a daily basis) and see for yourself.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 22:51:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-Cribl-always-produce-cooked-data/m-p/758993#M120310</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2026-03-03T22:51:21Z</dc:date>
    </item>
  </channel>
</rss>

