<?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: INGEST_EVAL for data coming from HEC at indexer layer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/INGEST-EVAL-for-data-coming-from-HEC-at-indexer-layer/m-p/678144#M113333</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;as transforms are handled on typing processor based on this picture&amp;nbsp;&lt;A href="https://www.aplura.com/assets/pdf/hec_pipelines.pdf" target="_blank"&gt;https://www.aplura.com/assets/pdf/hec_pipelines.pdf&lt;/A&gt;&amp;nbsp;it’s doable.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
    <pubDate>Tue, 20 Feb 2024 22:29:14 GMT</pubDate>
    <dc:creator>isoutamo</dc:creator>
    <dc:date>2024-02-20T22:29:14Z</dc:date>
    <item>
      <title>INGEST_EVAL for data coming from HEC at indexer layer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/INGEST-EVAL-for-data-coming-from-HEC-at-indexer-layer/m-p/678141#M113332</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please, in &lt;STRONG&gt;Splunk Enterprise,&amp;nbsp;&lt;/STRONG&gt;I would like to know if it is possible to apply an&amp;nbsp;&lt;STRONG&gt;INGEST_EVAL&lt;/STRONG&gt; processing at&amp;nbsp;&lt;STRONG&gt;indexer layer&lt;/STRONG&gt;&amp;nbsp;for data that is coming to indexer&amp;nbsp; from a&amp;nbsp;&lt;STRONG&gt;HEC&lt;/STRONG&gt; (http event collector).&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thanks&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 21:46:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/INGEST-EVAL-for-data-coming-from-HEC-at-indexer-layer/m-p/678141#M113332</guid>
      <dc:creator>cafissimo</dc:creator>
      <dc:date>2024-02-20T21:46:26Z</dc:date>
    </item>
    <item>
      <title>Re: INGEST_EVAL for data coming from HEC at indexer layer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/INGEST-EVAL-for-data-coming-from-HEC-at-indexer-layer/m-p/678144#M113333</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;as transforms are handled on typing processor based on this picture&amp;nbsp;&lt;A href="https://www.aplura.com/assets/pdf/hec_pipelines.pdf" target="_blank"&gt;https://www.aplura.com/assets/pdf/hec_pipelines.pdf&lt;/A&gt;&amp;nbsp;it’s doable.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 22:29:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/INGEST-EVAL-for-data-coming-from-HEC-at-indexer-layer/m-p/678144#M113333</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-02-20T22:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: INGEST_EVAL for data coming from HEC at indexer layer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/INGEST-EVAL-for-data-coming-from-HEC-at-indexer-layer/m-p/678147#M113334</link>
      <description>&lt;P&gt;Yep. +1 on that. HEC does skip some parts of the pipeline (line breaking, often timestamp recognition) but the index-time extractions and evals are applied normally.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 22:52:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/INGEST-EVAL-for-data-coming-from-HEC-at-indexer-layer/m-p/678147#M113334</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-02-20T22:52:58Z</dc:date>
    </item>
  </channel>
</rss>

