<?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 Am I over utilizing Props/Transforms? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Am-I-over-utilizing-Props-Transforms/m-p/540021#M90423</link>
    <description>&lt;P&gt;I'm going to describe a typical use case.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Software team will have one log file for most of it's outputs, lets call this HOUSES. This data will be generic health status information, transaction information, and some times data payloads in XML and some data in JSON. My practice has been to use a UF to monitor that file. Then on the Indexers i'll use Props to go through that data and set my time, linebreakser, and transforms.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then in my transforms I use REGEX to match UNIQ fields in the data like, for example, RED-HOUSE. This will grab all data from that original file that contains RED-HOUSE. I then do a sourcetype override and make the new source type HOUSES:RED-HOUSE.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then on my Searchhead i'll define my props/transforms (Using EXTRACT/REPORT) for field extractions.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll try to show a brief example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Data:&lt;/P&gt;&lt;P&gt;lets say sourcetype is LOGS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dcnsnoctads-1 2021/02/12 01:59:59.105 GMT-FANS ADS START PERIODIC PERIODIC TIMER_START .D00002
​
dcnsnoctads-1 2021/02/12 01:59:59.105 GMT-FANS ADS SEND PERIODIC CONTRACT REQUEST #502,  .D00002
​
dcnsnoctads-1 2021/02/12 01:59:59.105 GMT-FANS ADS PERIODIC PERIODIC CONTRACT TIMER_EXPIRED 0,.D00002&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On indexing Tier:&lt;/P&gt;&lt;P&gt;Props:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[LOGS]
SHOULD_LINEMERGE = False
TRANSFORMS-ADS = ADS, EFG, XYZ&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tranforms:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ADS]
REGEX = ADS
DEST_KEY = MetaData:sourcetype
FORMAT = sourcetype::LOGS:ADS&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Search head:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;props:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ADS]

REPORT-ADS = ADS_EXTRACTIONS&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(lets assume several data points use the same extraction, so REPORT should be used&amp;nbsp;&lt;/P&gt;&lt;P&gt;TRANSFORMS:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ADS_EXTRACTIONS]
REGEX = ADS (?P&amp;lt;ADS_Method&amp;gt;\w+\s\w+)\s(?P&amp;lt;ADS_Method_Type&amp;gt;\w+)\s(?P&amp;lt;Method_Message&amp;gt;\w+)(?:.*)(?P&amp;lt;tail_no&amp;gt;.{7}$)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this overkill? Or is this taking the right approach? I basically try to make a sourcetype for every differential of field extractions format there is.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 15 Feb 2021 21:13:03 GMT</pubDate>
    <dc:creator>ekenne06</dc:creator>
    <dc:date>2021-02-15T21:13:03Z</dc:date>
    <item>
      <title>Am I over utilizing Props/Transforms?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Am-I-over-utilizing-Props-Transforms/m-p/540021#M90423</link>
      <description>&lt;P&gt;I'm going to describe a typical use case.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Software team will have one log file for most of it's outputs, lets call this HOUSES. This data will be generic health status information, transaction information, and some times data payloads in XML and some data in JSON. My practice has been to use a UF to monitor that file. Then on the Indexers i'll use Props to go through that data and set my time, linebreakser, and transforms.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then in my transforms I use REGEX to match UNIQ fields in the data like, for example, RED-HOUSE. This will grab all data from that original file that contains RED-HOUSE. I then do a sourcetype override and make the new source type HOUSES:RED-HOUSE.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then on my Searchhead i'll define my props/transforms (Using EXTRACT/REPORT) for field extractions.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll try to show a brief example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Data:&lt;/P&gt;&lt;P&gt;lets say sourcetype is LOGS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dcnsnoctads-1 2021/02/12 01:59:59.105 GMT-FANS ADS START PERIODIC PERIODIC TIMER_START .D00002
​
dcnsnoctads-1 2021/02/12 01:59:59.105 GMT-FANS ADS SEND PERIODIC CONTRACT REQUEST #502,  .D00002
​
dcnsnoctads-1 2021/02/12 01:59:59.105 GMT-FANS ADS PERIODIC PERIODIC CONTRACT TIMER_EXPIRED 0,.D00002&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On indexing Tier:&lt;/P&gt;&lt;P&gt;Props:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[LOGS]
SHOULD_LINEMERGE = False
TRANSFORMS-ADS = ADS, EFG, XYZ&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tranforms:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ADS]
REGEX = ADS
DEST_KEY = MetaData:sourcetype
FORMAT = sourcetype::LOGS:ADS&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Search head:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;props:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ADS]

REPORT-ADS = ADS_EXTRACTIONS&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(lets assume several data points use the same extraction, so REPORT should be used&amp;nbsp;&lt;/P&gt;&lt;P&gt;TRANSFORMS:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ADS_EXTRACTIONS]
REGEX = ADS (?P&amp;lt;ADS_Method&amp;gt;\w+\s\w+)\s(?P&amp;lt;ADS_Method_Type&amp;gt;\w+)\s(?P&amp;lt;Method_Message&amp;gt;\w+)(?:.*)(?P&amp;lt;tail_no&amp;gt;.{7}$)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this overkill? Or is this taking the right approach? I basically try to make a sourcetype for every differential of field extractions format there is.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Feb 2021 21:13:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Am-I-over-utilizing-Props-Transforms/m-p/540021#M90423</guid>
      <dc:creator>ekenne06</dc:creator>
      <dc:date>2021-02-15T21:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: Am I over utilizing Props/Transforms?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Am-I-over-utilizing-Props-Transforms/m-p/540032#M90426</link>
      <description>&lt;P&gt;Sourcetypes tell Splunk how to parse events into fields.&amp;nbsp; If an event doesn't work with the existing sourcetypes (and the sourcetype can't be made to work) then create a new one that does.&lt;/P&gt;&lt;P&gt;Consider un-friending your developers until they come up with a sane method of logging.&amp;nbsp;&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2021 01:16:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Am-I-over-utilizing-Props-Transforms/m-p/540032#M90426</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-02-16T01:16:09Z</dc:date>
    </item>
  </channel>
</rss>

