<?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 Help with Lookup table in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Help-with-Lookup-table/m-p/69439#M180522</link>
    <description>&lt;P&gt;I am attempting to display categories from websense logs in human readable form. Currently they display the category id in the Search app rather than the name. I added a lookup table with two columns, one with the category, and one with the category name, comma delimited to achieve this.&lt;/P&gt;

&lt;P&gt;Here is my addition to props.conf:&lt;/P&gt;

&lt;P&gt;[websense_categories] &lt;BR /&gt;
LOOKUP-websense = websense category OUTPUT category_name &lt;BR /&gt;
FIELDALIAS-category = category_name&lt;/P&gt;

&lt;P&gt;And to transforms.conf:&lt;/P&gt;

&lt;P&gt;[websense]&lt;BR /&gt;
DELIMS = ","&lt;BR /&gt;
FIELDS = "category", "category_name"&lt;BR /&gt;
filename = websense.csv&lt;BR /&gt;
max_matches = 100&lt;/P&gt;

&lt;P&gt;Still when searching websense logs via search app categories appear as numbers rather than the category name. If more information is needed, I can clarify. Thank you,&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 13:34:03 GMT</pubDate>
    <dc:creator>pgissiner</dc:creator>
    <dc:date>2020-09-28T13:34:03Z</dc:date>
    <item>
      <title>Help with Lookup table</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-with-Lookup-table/m-p/69439#M180522</link>
      <description>&lt;P&gt;I am attempting to display categories from websense logs in human readable form. Currently they display the category id in the Search app rather than the name. I added a lookup table with two columns, one with the category, and one with the category name, comma delimited to achieve this.&lt;/P&gt;

&lt;P&gt;Here is my addition to props.conf:&lt;/P&gt;

&lt;P&gt;[websense_categories] &lt;BR /&gt;
LOOKUP-websense = websense category OUTPUT category_name &lt;BR /&gt;
FIELDALIAS-category = category_name&lt;/P&gt;

&lt;P&gt;And to transforms.conf:&lt;/P&gt;

&lt;P&gt;[websense]&lt;BR /&gt;
DELIMS = ","&lt;BR /&gt;
FIELDS = "category", "category_name"&lt;BR /&gt;
filename = websense.csv&lt;BR /&gt;
max_matches = 100&lt;/P&gt;

&lt;P&gt;Still when searching websense logs via search app categories appear as numbers rather than the category name. If more information is needed, I can clarify. Thank you,&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:34:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-with-Lookup-table/m-p/69439#M180522</guid>
      <dc:creator>pgissiner</dc:creator>
      <dc:date>2020-09-28T13:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: Help with Lookup table</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Help-with-Lookup-table/m-p/69440#M180523</link>
      <description>&lt;P&gt;I believe that you are mixing two concepts; &lt;CODE&gt;REPORT&lt;/CODE&gt; and &lt;CODE&gt;LOOKUP&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;DELIMS&lt;/CODE&gt; and &lt;CODE&gt;FIELDS&lt;/CODE&gt; in transforms.conf would typically be used in a REPORT (from &lt;CODE&gt;props.conf&lt;/CODE&gt;)&lt;/P&gt;

&lt;P&gt;The &lt;CODE&gt;FIELDALIAS&lt;/CODE&gt; also misses stuff. It should be;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FIELDALIAS-somename original_field_name AS alternate_field_name 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;See the &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.2/Admin/Propsconf"&gt;docs for props.conf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;As for the &lt;CODE&gt;LOOKUP&lt;/CODE&gt; itself, you should see the &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.1/Knowledge/Addfieldsfromexternaldatasources#Example_of_static_fields_lookup"&gt;example regarding HTTP status lookups in the docs&lt;/A&gt;.&lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;Kristian&lt;/P&gt;</description>
      <pubDate>Thu, 21 Mar 2013 14:22:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Help-with-Lookup-table/m-p/69440#M180523</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-03-21T14:22:17Z</dc:date>
    </item>
  </channel>
</rss>

