Splunk Enterprise

Simple method to truncate Cisco ISE syslogs to 2000 characters to reduce Splunk database size

anthonyi
Explorer

Hello.

I cannot find an answer to this simple question, although I have found other information utilizing props.conf and transforms in more complicated situations.

I currently have a single Splunk instance as an all-in-one solution, and I am looking for a simple method to truncate ISE logs to 2000 characters to lower Splunk database size. ISE itself is not capable of this.

I am very familiar with Splunk via GUI, but not at all with modifying the configuration files, so step by step instructions would be very helpful.

Thanks in advance.

Labels (1)
0 Karma
1 Solution

kiran_panchavat
Champion

@anthonyi 

Identify the sourcetype of your Cisco ISE logs. Common sourcetypes for ISE are cisco:ise:syslog.. You can
confirm this in Splunk’s GUI or CLI.
 
GUI: 
 
  • Go to Search & Reporting.
  • Run a search like index=<indexname>
  • Check the sourcetype field in the events to note the exact name (e.g., cisco:ise:syslog).

CLI:

The sourcetype for Cisco ISE can be identified in the inputs.conf file through the CLI.

Edit props.conf to Truncate Events, You can find out the props.conf details using the below command:
 
/opt/splunk/bin/splunk btool props list --debug 
 
For instance, if you have the props.conf file located in /opt/splunk/etc/system/local, you can configure it with the following settings:
 
vi /opt/splunk/etc/system/local/props.conf 
 
Add the following stanza to set the TRUNCATE parameter for your ISE logs:
 
[your_sourcetype]
TRUNCATE = 2000
 
For example, if your ISE logs have a sourcetype of cisco:ise:syslog, the stanza would be:
 
[cisco:ise:syslog]
TRUNCATE = 2000
This setting ensures that any event exceeding 2000 bytes will be truncated, effectively reducing the size of each event stored in Splunk.
 
After saving the changes to props.conf, restart your Splunk instance to apply the new configuration.
 
/opt/splunk/bin/splunk restart
 
NOTE: 
If this add-on is not yet installed, please proceed with the installation. it https://splunkbase.splunk.com/app/1915 
 
Reference for sourcetypes:
 
Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

View solution in original post

kiran_panchavat
Champion

@anthonyi 

Identify the sourcetype of your Cisco ISE logs. Common sourcetypes for ISE are cisco:ise:syslog.. You can
confirm this in Splunk’s GUI or CLI.
 
GUI: 
 
  • Go to Search & Reporting.
  • Run a search like index=<indexname>
  • Check the sourcetype field in the events to note the exact name (e.g., cisco:ise:syslog).

CLI:

The sourcetype for Cisco ISE can be identified in the inputs.conf file through the CLI.

Edit props.conf to Truncate Events, You can find out the props.conf details using the below command:
 
/opt/splunk/bin/splunk btool props list --debug 
 
For instance, if you have the props.conf file located in /opt/splunk/etc/system/local, you can configure it with the following settings:
 
vi /opt/splunk/etc/system/local/props.conf 
 
Add the following stanza to set the TRUNCATE parameter for your ISE logs:
 
[your_sourcetype]
TRUNCATE = 2000
 
For example, if your ISE logs have a sourcetype of cisco:ise:syslog, the stanza would be:
 
[cisco:ise:syslog]
TRUNCATE = 2000
This setting ensures that any event exceeding 2000 bytes will be truncated, effectively reducing the size of each event stored in Splunk.
 
After saving the changes to props.conf, restart your Splunk instance to apply the new configuration.
 
/opt/splunk/bin/splunk restart
 
NOTE: 
If this add-on is not yet installed, please proceed with the installation. it https://splunkbase.splunk.com/app/1915 
 
Reference for sourcetypes:
 
Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

livehybrid
SplunkTrust
SplunkTrust

Hi @anthonyi

Are you using an on-premise or Splunk Cloud environment?

If you're using Splunk Cloud: 

In the Splunk UI, go to Settings -> sourcetypes.

Find/click the sourcetype you want to restrict the length of, then click the "Advanced" tab.

If there is already a "TRUNCATE" value then update this to 2000 and hit save.

If there isnt then click "New Setting" at the bottom and then enter TRUNCATE for the name and 2000 for the value.

If you are running on-premise then its unlikely you'll be able to make the changes in this way unless you are using a all-in-one instance, which generally wouldnt be used for production.

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

0 Karma

anthonyi
Explorer

Thanks. On prem. All-in-one.

0 Karma

livehybrid
SplunkTrust
SplunkTrust

Great, in that case you should be able to make the changes in the UI if preferred.

Did this work for you?

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...