Getting Data In

Transforms not replacing original value

thard_splunk
Splunk Employee
Splunk Employee

Hello,

I have a CSV in which I am attempting to shorten a 128 character string down to the last 8 characters. I used the following configuration in transforms/props:

props.conf:

[taxi_csv]
DATETIME_CONFIG =
INDEXED_EXTRACTIONS = csv
KV_MODE = none
NO_BINARY_CHECK = true
SHOULD_LINEMERGE = false
category = Structured
disabled = false
pulldown_type = true
description = Comma-separated value format. Set header and other settings in "D$
TIMESTAMP_FIELDS = Trip Start Timestamp
TZ = America/Chicago
TRANSFORM-mask = taxiMask

transforms.conf:

[taxiMask]
REGEX = (\w{120})(\w{8})
FORMAT = "Taxi ID"::$2
WRITE_META = true
SOURCE_KEY = field:"Taxi ID"
DEST_KEY = _raw

However, the resulting indexed data contains both the original string and the shortened string as two separate values in the same field. What configuration change can I make to replace the original value with the shortened string?

Thanks!

0 Karma

somesoni2
Revered Legend

Try this for your transforms.conf entry

[taxiMask]
REGEX = (?m)^(.*)(\w{120})(\w{8})(.*)$
FORMAT = $1$3$4
DEST_KEY = _raw
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!

Splunk Enterprise Security: An Automated Phishing Response Workflow

Originally posted on Splunk.com.   Key takeaways  The volume of phishing emails can overwhelm even the most ...

Sharper ES Detections, Agentic AI Integrations, Smarter Workload Management, and More ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...