<?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 How to create a custom CEF index for CEF Syslog data and extract token field field names and values? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-create-a-custom-CEF-index-for-CEF-Syslog-data-and-extract/m-p/150380#M42140</link>
    <description>&lt;P&gt;I'm looking for help on creating a custom CEF index. &lt;/P&gt;

&lt;P&gt;I have CEF Syslog data sent into my Splunk instance and I'd like to index some of the tokened fields and simply parse the others. &lt;/P&gt;

&lt;P&gt;I know how to do regex extractions for each field, but there has to be a better way to tell splunk there is a CEF header and following a header is the token field names and values. &lt;/P&gt;

&lt;P&gt;I want these to be indexed prior to searching for performance. &lt;/P&gt;

&lt;P&gt;I do not know if this will scale, but I want to try it. &lt;/P&gt;

&lt;P&gt;Can anyone help?&lt;/P&gt;</description>
    <pubDate>Tue, 24 Feb 2015 17:31:18 GMT</pubDate>
    <dc:creator>grantsales</dc:creator>
    <dc:date>2015-02-24T17:31:18Z</dc:date>
    <item>
      <title>How to create a custom CEF index for CEF Syslog data and extract token field field names and values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-create-a-custom-CEF-index-for-CEF-Syslog-data-and-extract/m-p/150380#M42140</link>
      <description>&lt;P&gt;I'm looking for help on creating a custom CEF index. &lt;/P&gt;

&lt;P&gt;I have CEF Syslog data sent into my Splunk instance and I'd like to index some of the tokened fields and simply parse the others. &lt;/P&gt;

&lt;P&gt;I know how to do regex extractions for each field, but there has to be a better way to tell splunk there is a CEF header and following a header is the token field names and values. &lt;/P&gt;

&lt;P&gt;I want these to be indexed prior to searching for performance. &lt;/P&gt;

&lt;P&gt;I do not know if this will scale, but I want to try it. &lt;/P&gt;

&lt;P&gt;Can anyone help?&lt;/P&gt;</description>
      <pubDate>Tue, 24 Feb 2015 17:31:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-create-a-custom-CEF-index-for-CEF-Syslog-data-and-extract/m-p/150380#M42140</guid>
      <dc:creator>grantsales</dc:creator>
      <dc:date>2015-02-24T17:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to create a custom CEF index for CEF Syslog data and extract token field field names and values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-create-a-custom-CEF-index-for-CEF-Syslog-data-and-extract/m-p/150381#M42141</link>
      <description>&lt;P&gt;I know this is an 'older' question, but I am getting into the possibility that I too will be working with CEF data. II take it that what you refer to as the "tokened fields" that you mean the "cs#=" and the "cs#label=" fields that are in the "Extension" portion of the messages.&lt;/P&gt;

&lt;P&gt;I have not seen anything that indicates there is a way for Splunk to auto-ingest/field extract CEF data. You will likely need to create a transforms to do that and the RegEx should be fairly straight forward for that.&lt;/P&gt;

&lt;P&gt;More importantly, I am not sure you'd want to extract these fields at index time; the savings you'd get at search time with this is not likely to be worth the performance impact on index processing to do the extraction and indexing together. I suggest you keep to search time field extractions.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Nov 2015 17:35:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-create-a-custom-CEF-index-for-CEF-Syslog-data-and-extract/m-p/150381#M42141</guid>
      <dc:creator>curryRick</dc:creator>
      <dc:date>2015-11-09T17:35:25Z</dc:date>
    </item>
  </channel>
</rss>

