Getting Data In

How to edit a props.conf for an aribitrary source?

minkyuk
Explorer

Where do I go & how should I do it?

I know what to change,

[$sourcetype]
MAX_EVENT = 100000

I would appreciate your help,

A newcomer

Tags (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

The file to edit is SPLUNK_HOME/etc/system/local/props.conf. If it doesn't exist, create one. DO NOT edit default/props.conf! Use the text editor of your choice to do the editing.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

The file to edit is SPLUNK_HOME/etc/system/local/props.conf. If it doesn't exist, create one. DO NOT edit default/props.conf! Use the text editor of your choice to do the editing.

---
If this reply helps you, Karma would be appreciated.

minkyuk
Explorer

Do I put the line in a search head?

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Put it on the indexer(s). Remember to restart Splunk after making the change.

---
If this reply helps you, Karma would be appreciated.
0 Karma

minkyuk
Explorer

Sorry, but do you mean at time of "Adding Data?"

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Whenever you modify a .conf file outside the Splunk GUI, Splunk must be restarted to incorporate the change.

---
If this reply helps you, Karma would be appreciated.
0 Karma

minkyuk
Explorer

like, index setting section?

0 Karma

solarboyz1
Builder

props.conf can be found in a few places:

$SPLUNK_HOME/etc/system/default - Default props (do not modify)
$SPLUNK_HOME/etc/system/local - Should be used for adjustments that are only needed on THIS system
$SPLUNK_HOME/etc/apps/{APPNAME}/default - An apps default props.conf (do not modify)
$SPLUNK_HOME/etc/apps/{APPNAME}/local - Customization of an apps props.conf.

If there isn't a props.conf under the local directory, a new file should be created.

We use the following guidelines:

  1. If the modification is to props.conf implemented by an App, it should be in that apps local/props.conf
  2. If the modification is a standalone change, we put it in one of the Apps created for our environment that are then pushed using the deployment server

If you are looking for where the props.conf for a specific sourcetype are defined you can use the btool command:

For all props:
$SPLUNK_HOME/bin/splunk cmd btool --debug props list

For the props to a specific sourcetype:
$SPLUNK_HOME/bin/splunk cmd btool --debug props list $sourcetype

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...