I would like to hear from other admins on how they are keeping up with high demand of data onboarding requests into their Splunk instance in large organizations. We are battling with more than 300 requests per month to onboard data into Splunk as every application in the organization wants to utilize Splunk for monitoring and the demand only keeps increasing. Most of these are custom application logs. The biggest bottleneck is defining props (LINE BREAKER, TIME STAMP etc..,) for the source types by having to manually analyze each individual log. Other parts of the onboarding (inputs.conf, indexes.conf etc..,) can be easily automated for seamless onboarding but not props. Not defining props for source types to leave to Splunk defaults is not an option as we have seen some serious performance issues on indexers. I would like to hear from Splunk if there is a strategic direction in this regard to make admins life easier with respect to onboarding and other admins who might have dealt with similar situation and overcome in creative ways. Regards, Pradeep
... View more