Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Re: Inline field extracted vs Transformation?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am walking through the Cisco app and I noticed that there are a lot different ways fields are being extracted. It looks like there are many inline extractions and others referencing a transform, all in the props.conf, (EXTRACT vs REPORT). I have seen bits and pieces on what is the difference is between the two methods, but it still is unclear to me.
My question is, what are the pros and cons of doing an inline EXTRACT versus doing a transformation and reference it with a REPORT in the props. conf, and vice versa.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
They are the same except that EXTRACT is inlined so only exists in props.conf whereas REPORT is 2-part with half in props.conf and the other half in transforms.conf. If later extractions depend on other extractions, you should definitely use REPORT so that you can clearly control which ones happen first. Also, if you have the same extractions for multiple sourcetypes, it is easier to have a single copy in transforms.conf so that any changes/fixes to it are done on 1 line in 1 file instead of on multiple lines in multiple files. Honestly, EXTRACT is lazy; I always do REPORT; I cannot think of any real advantage to EXTRACT.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
They are the same except that EXTRACT is inlined so only exists in props.conf whereas REPORT is 2-part with half in props.conf and the other half in transforms.conf. If later extractions depend on other extractions, you should definitely use REPORT so that you can clearly control which ones happen first. Also, if you have the same extractions for multiple sourcetypes, it is easier to have a single copy in transforms.conf so that any changes/fixes to it are done on 1 line in 1 file instead of on multiple lines in multiple files. Honestly, EXTRACT is lazy; I always do REPORT; I cannot think of any real advantage to EXTRACT.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please in better understanding, what is the actual difference between prof.conf and transforms.conf file?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I never heard of prof.conf but in any case, you should ask your own new question.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Agent Mode Engaged! Enchaining Agentic Operations with Splunk AI Assistant 2.0
Announcing Modern Navigation: A New Era of Splunk User Experience
Modernize your Splunk Apps – Introducing Python 3.13 in Splunk
