I have transforms like access-extractions and access-request, which map to the automatically recognized source types like access_combined, access_combined_wcookie, and access_common in the Field Extractions. Fields from events with these sourcetypes have fields extracted at search time as they should. However, the automatically recognized source types list also mentions: websphere_trlog_syserr and websphere_trlog_sysout. I have a websphere_trlog but not the other two. These should be built-in and not require any other specific app, right? Why would I be missing these two?
Splunk version 6.4.3
You should never, Never, NEVER rely on Splunk's automatic sourcetyping feature (IMHO this should be deprecated and removed). You, as the admin, should ALWAYS manually sourcetype everything that you forward into splunk and you should consult and conform to this document:
YOU should be the one to do this mapping with a
sourcetype=<foo> inside of EVERY stanza in EVERY
Thanks woodcock - that's some pretty strong wording. 🙂
The sourcetypes don't currently conform to the document so they'll need to be renamed. Regardless, once this is done, I still want Splunk to properly extract fields at search time but there's no definition for these sourcetypes in props.conf.
What would cause this? The extractions should be available by default, correct? Hence "pretrained sourcetypes."
This product is not a magic 8-ball or genie in a bottle; it can't know everything. Check splunkbase for an app related to your source/sourcetype; if you are using enterprise software, it is probably there. If not, you will have to build your own field extractions or force the product to output it's stuff in something Splunk automatically groks like
Agree - there's no such thing as a "silver bullet." However, I guess my question comes down to: Is there a built-in extraction for all of the pretrained sourcetypes? I assumed there was; otherwise, what's the point of the "pretrained?"