<?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: Transformation fields using Splunk UI in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356287#M165937</link>
    <description>&lt;P&gt;You may want a transform. You may want a field extraction. They are similar. If the fields you want are related to a sourcetype, or to a source, then do a field extraction. If you want it to happen on any data, then do a transform.&lt;/P&gt;

&lt;P&gt;But, I can't help you without an example data to look at. Just to look for a string and then make a field could be useful, and may not be. I assume from your description that you could have something other than &lt;CODE&gt;Agreed&lt;/CODE&gt; as a value for &lt;CODE&gt;Decision&lt;/CODE&gt;, otherwise you would never care about doing a field extraction. What you ask for without an example is equivalent to marking everything blue that you see as your favorite car. &lt;/P&gt;</description>
    <pubDate>Sun, 24 Sep 2017 21:30:29 GMT</pubDate>
    <dc:creator>cpetterborg</dc:creator>
    <dc:date>2017-09-24T21:30:29Z</dc:date>
    <item>
      <title>Transformation fields using Splunk UI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356281#M165931</link>
      <description>&lt;P&gt;Team,&lt;BR /&gt;
I need help in defining 3 new fields using Splunk User interface.&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Decision=Agree , Field Name should be "Decision"  and Matching values is "Agree". &lt;/LI&gt;
&lt;LI&gt;Fieldname is "Time" , need this in the Timestamp format ( Dateand HH:MM:SS)&lt;/LI&gt;
&lt;LI&gt;SourceIP&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Any help is greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 24 Sep 2017 00:38:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356281#M165931</guid>
      <dc:creator>veera9</dc:creator>
      <dc:date>2017-09-24T00:38:52Z</dc:date>
    </item>
    <item>
      <title>Re: Transformation fields using Splunk UI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356282#M165932</link>
      <description>&lt;P&gt;1- Not clear, assuming you have a field, say X which has 'agree' and other values, if so try&lt;BR /&gt;
eval Decision=Case(X="Agree","Decision")&lt;BR /&gt;
2- eval Time=strftime(_time,"%d %H:%M:%S"). Are you missing year and/ or month components?&lt;BR /&gt;
3- Witthout looking at your data its is hard to say but have you looked at this? ip extraction is very common question answered many times befre&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/49448/extract-ip-address-with-rex-or-trim.html"&gt;https://answers.splunk.com/answers/49448/extract-ip-address-with-rex-or-trim.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/48882/need-to-extract-ip-address.html"&gt;https://answers.splunk.com/answers/48882/need-to-extract-ip-address.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/438684/rex-ip-address-extraction.html"&gt;https://answers.splunk.com/answers/438684/rex-ip-address-extraction.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 24 Sep 2017 11:44:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356282#M165932</guid>
      <dc:creator>Sukisen1981</dc:creator>
      <dc:date>2017-09-24T11:44:14Z</dc:date>
    </item>
    <item>
      <title>Re: Transformation fields using Splunk UI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356283#M165933</link>
      <description>&lt;P&gt;As @Sukisen1981 says, example data is needed. Without it, almost any answer will be a shot in the dark. You can obfuscate the data, but don't change the nature of it so that it is useful in helping you.&lt;/P&gt;</description>
      <pubDate>Sun, 24 Sep 2017 13:25:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356283#M165933</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2017-09-24T13:25:22Z</dc:date>
    </item>
    <item>
      <title>Re: Transformation fields using Splunk UI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356284#M165934</link>
      <description>&lt;P&gt;Is it OK to use "eval" in the Splunk field transformation UI?&lt;/P&gt;</description>
      <pubDate>Sun, 24 Sep 2017 15:39:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356284#M165934</guid>
      <dc:creator>veera9</dc:creator>
      <dc:date>2017-09-24T15:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: Transformation fields using Splunk UI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356285#M165935</link>
      <description>&lt;P&gt;As far as I know there is no way to do eval type expression in the Transformations. Not in the UI, or in the .conf files.&lt;/P&gt;</description>
      <pubDate>Sun, 24 Sep 2017 19:47:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356285#M165935</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2017-09-24T19:47:07Z</dc:date>
    </item>
    <item>
      <title>Re: Transformation fields using Splunk UI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356286#M165936</link>
      <description>&lt;P&gt;Thank you so much. Below are my requirements:&lt;/P&gt;

&lt;P&gt;I want to define a field using the UI in Field Transformations in Field settings:&lt;/P&gt;

&lt;P&gt;The field need to match a string value ex: "Agreed". I want the field name to be defined as "Decision".&lt;/P&gt;

&lt;P&gt;When I search in the search box, I want the field "Decision" to appear in the list of fields.&lt;BR /&gt;
Thank you for your time.&lt;BR /&gt;
Raghu&lt;/P&gt;</description>
      <pubDate>Sun, 24 Sep 2017 20:21:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356286#M165936</guid>
      <dc:creator>veera9</dc:creator>
      <dc:date>2017-09-24T20:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: Transformation fields using Splunk UI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356287#M165937</link>
      <description>&lt;P&gt;You may want a transform. You may want a field extraction. They are similar. If the fields you want are related to a sourcetype, or to a source, then do a field extraction. If you want it to happen on any data, then do a transform.&lt;/P&gt;

&lt;P&gt;But, I can't help you without an example data to look at. Just to look for a string and then make a field could be useful, and may not be. I assume from your description that you could have something other than &lt;CODE&gt;Agreed&lt;/CODE&gt; as a value for &lt;CODE&gt;Decision&lt;/CODE&gt;, otherwise you would never care about doing a field extraction. What you ask for without an example is equivalent to marking everything blue that you see as your favorite car. &lt;/P&gt;</description>
      <pubDate>Sun, 24 Sep 2017 21:30:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Transformation-fields-using-Splunk-UI/m-p/356287#M165937</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2017-09-24T21:30:29Z</dc:date>
    </item>
  </channel>
</rss>

