Getting Data In

New SourceType and pushing out

willadams
Contributor

I have a requirement to duplicate a default SPLUNK sourcetype. The duplicate sourcetype is based on the JSON sourcetype. Effectively my new sourcetype is configured as follows

[json:myapp]
INDEXED_EXTRACTIONS = JSON
TIMESTAMP_FIELDS = date
TIME_FORMAT = %Y%m%d
TZ = ****** [redacted]
detect_trailing_nulls = auto
SHOULD_LINEMERGE = false
KV_MODE = none
AUTO_KV_JSON = false 

My question is around deploying this to my distributed environment. The above configuration on a standalone instance would be to create a local props.conf under etc/system/local with this inserted. However in a distributed environment (with Cluster Masters, Index Cluster, search heads etc.) should this be deployed as a typical app or must I manually adjust each instance in my environment to pick this up. It is not being handled differently to standard JSON so hence using the same transforms that JSON would use hence the INDEXED_TRANSACTIONS are no different. The only item being added in this line is the Time Zone. I am not changing the whole JSON as this one particular device I need to handle differently to everything else, hence the need. The question is more around the default duplication of existing sourcetypes.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Add your custom sourcetype to a custom app then deploy the app to all instances via the Deployment Server, Cluster Master, and SHC Deployer. Deployment to all instances perhaps is more than is necessary, but doesn't hurt and means the props are available wherever they are needed.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...