Getting Data In

Input files have changed format, so how do I edit my configurations to keep the old data and handle the new data?

splunkmasterfle
Path Finder

Hi,

Here is my situation (and I know it isn't ideal, but I have to work with it for now)

I have scripts that pre-process log files to a standard format that Splunk digests. The format isn't really that important here, but the problem is that I have to add two more fields to this file that is created.

How do I handle this change in the format of my input file with the setup that I currently have?

I want the old data to remain unchanged and also perhaps add a default value for the 2 new fields ?

inputs.conf

[monitor:///var/log/error-monitoring]
followTail = 0
sourcetype = psv
host =
host_regex = ([^/.]+).
index = test-index

props.conf

[psv]
REPORT-PSV = psv-delim
pulldown_type = 1
NO_BINARY_CHECK = 1
SHOULD_LINEMERGE = false
TIME_FORMAT = %Y-%m-%d %H:%M:%S,%3N

transforms.conf

[psv-delim]
DELIMS = "|"
FIELDS = server,service,date,type,requestId,class,message

....

So essentially my new input file would have server,service,date,type,requestId,class,message,user,id

Halp.

0 Karma

s2_splunk
Splunk Employee
Splunk Employee

You should just be able to add the two fields in transforms.conf without impacting existing events that don't contain data for those fields.
To get default values assigned to those two fields for older events, you can setup two calculated fields for your sourcetype, like so:

fieldname: user
eval: if(isNull( user, "defaultUser", user ))

Do the same thing for your default id.

BTW, I'd recommend picking a more descriptive name for your sourcetype. PSV describes the format, not so much the content. Maybe something like [ErrorMonitoring]. In most cases, that makes it easier for users having an idea what the data is that they are looking at. Just a thought.

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!

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 ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...