<?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: Transform on extracted field in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131933#M7486</link>
    <description>&lt;P&gt;Hi. my regex works fine, using rex and as a transform, if I run it on the "_raw" field.  It runs fine using rex against the extracted "message" field.  I just can't get it to run as a transform against the "message" field.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Feb 2014 13:46:37 GMT</pubDate>
    <dc:creator>pixelseventy2</dc:creator>
    <dc:date>2014-02-05T13:46:37Z</dc:date>
    <item>
      <title>Transform on extracted field</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131930#M7483</link>
      <description>&lt;P&gt;Hi.  I'm using OSSEC to send logs from a variety of sources by syslog to Splunk.  I've created transforms to extract the fields, the main one of which gets extracted as "message".  One of the log sources is ISA Server, and I'm trying to do some extractions on those fields.  I've got a transform to change the "host" to the original host, not the OSSEC server. Everything has the same sourcetype, which I tried to change using a "[host::" entry in props.conf, but this failed because, I think, it's looking at the original host, not the transformed one.&lt;/P&gt;

&lt;P&gt;I can get an extraction to work against the "_raw" field, by not against the "message" field.  Is it possible to get an extract to work against a field extracted an search time?  I've tried referencing the field as "message" and "field:message", but the extract fails.  I can get a more accurate regex if I can reference this field.&lt;/P&gt;

&lt;P&gt;Alternatively, and this might be better, is to use a delimiter transform rather than regex if I can get that to work on the "message" field, but I need to be able selectively target just the ISA logs.&lt;/P&gt;

&lt;P&gt;Hope this makes some sense.&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2014 16:22:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131930#M7483</guid>
      <dc:creator>pixelseventy2</dc:creator>
      <dc:date>2014-01-30T16:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: Transform on extracted field</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131931#M7484</link>
      <description>&lt;P&gt;Your question makes sense - but a lot of us are not familiar with OSSEC or the ISA Server logs. A few lines of the log would be &lt;EM&gt;very&lt;/EM&gt; helpful! Otherwise, only a subset of the folks on this forum will be able to answer your question.&lt;/P&gt;

&lt;P&gt;Also, the relevant props.conf and transforms.conf stanzas would be helpful as well.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2014 17:14:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131931#M7484</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-01-30T17:14:11Z</dc:date>
    </item>
    <item>
      <title>Re: Transform on extracted field</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131932#M7485</link>
      <description>&lt;P&gt;I would first recommend checking the regex from the search bar to validate the field extraction works. Then, once working, you could move it to props and transforms.&lt;/P&gt;

&lt;P&gt;i.e.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;your search | rex field=message (?&amp;lt;my_field&amp;gt;my capture pattern here)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 31 Jan 2014 05:57:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131932#M7485</guid>
      <dc:creator>bandit</dc:creator>
      <dc:date>2014-01-31T05:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: Transform on extracted field</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131933#M7486</link>
      <description>&lt;P&gt;Hi. my regex works fine, using rex and as a transform, if I run it on the "_raw" field.  It runs fine using rex against the extracted "message" field.  I just can't get it to run as a transform against the "message" field.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Feb 2014 13:46:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131933#M7486</guid>
      <dc:creator>pixelseventy2</dc:creator>
      <dc:date>2014-02-05T13:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: Transform on extracted field</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131934#M7487</link>
      <description>&lt;P&gt;Hi. OSSEC is a log server, which collects logs and forwards alerts using syslog.  ISA logs look like this as they are forwarded, the "message" field is tab-delimited:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;Feb  3 08:40:19 log-01 ossec: crit=3&lt;BR /&gt;
id=108001 description="ISA Internet&lt;BR /&gt;
access permitted" component="(isa01)&lt;BR /&gt;
172.19.1.1-&amp;gt;\ISALogs\ISALOG_20140203_WEB_000.w3c",&lt;BR /&gt;
classification=" proxy,allowed,",&lt;BR /&gt;
src_ip="172.19.2.2", acct="anonymous",&lt;BR /&gt;
message="172.19.2.2     anonymous ... 0x800 &lt;BR /&gt;
Allowed"&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;Sorry, ISA Logs are too long to post here in full ...&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:48:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131934#M7487</guid>
      <dc:creator>pixelseventy2</dc:creator>
      <dc:date>2020-09-28T15:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: Transform on extracted field</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131935#M7488</link>
      <description>&lt;P&gt;In props.conf I had:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;[ossec_alerts]&lt;BR /&gt;
REPORT-ossec-isa = ossec-splunk-isa&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;in transforms.conf I tried a number of permutations, but what I want is:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;[ossec-splunk-isa]&lt;BR /&gt;
SOURCE_KEY = field:message&lt;BR /&gt;
REGEX = ^\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}\t[^\t]+\t(?P&lt;AGENT&gt;.*?)\t\d{4}-\d{2}-\d{2}\t\d{2}:\d{2}:\d{2}\t[^\t]+\t[^\t]+\t(?P&lt;R_HOST&gt;[^\t]+)\t\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}\t&lt;/R_HOST&gt;&lt;/AGENT&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:48:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131935#M7488</guid>
      <dc:creator>pixelseventy2</dc:creator>
      <dc:date>2020-09-28T15:48:33Z</dc:date>
    </item>
    <item>
      <title>Re: Transform on extracted field</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131936#M7489</link>
      <description>&lt;P&gt;A-ha! What you are asking is to create a new field based on an existing field - when both fields are extracted at search time!&lt;/P&gt;

&lt;P&gt;AFAIK, this is not possible in &lt;CODE&gt;props.conf&lt;/CODE&gt; or &lt;CODE&gt;transforms.conf&lt;/CODE&gt; - but you can do it with the &lt;CODE&gt;rex&lt;/CODE&gt; command, as Rob illustrates above.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2014 23:57:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Transform-on-extracted-field/m-p/131936#M7489</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2014-02-11T23:57:51Z</dc:date>
    </item>
  </channel>
</rss>

