Splunk Search

Why doesn't replace work on a nested field?

YatMan
Explorer

Sample event

 

{ 
    durationMs:  83  
    properties:  { 
        url:  https://mywebsite/v1/organization/41547/buildings
    } 
   correlationId: e581d476-fa5f-4023-a53e-53d6e06734ae
}

 


I want to replace the ids into
https://mywebsite/v1/organization/{id}/buildings

I tried {base search string} | eval endpoint=replace(properties.url, "\d+", "{id}") | stats by endpoint 
This return no result, but if I try other coorelationId field on the root level, {base search string} | eval endpoint=replace(coorelationId, "\d+", "{id}") | stats by endpoint  

This return what I expected
endpoint                   |   (other fields)
adb{id}f{id}-{id}fd{id}-{id}-a{id}b-{id}c{id}f{id}d | (other fields)
aea{id}e{id}c-fcdc-{id}-a{id}-{id}a{id}bfe{id}ee{id} | (other fields)

Why replace doesn't work on nested field?

Labels (1)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

Field names with dots in or other special characters need to be in single quotes. Try this

| eval endpoint=replace('properties.url', "\d+", "{id}")

View solution in original post

ITWhisperer
SplunkTrust
SplunkTrust

Field names with dots in or other special characters need to be in single quotes. Try this

| eval endpoint=replace('properties.url', "\d+", "{id}")

YatMan
Explorer

this single quote solution works well. thank you.
It would be helpful if you guys can add an example in the document, thanks! https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Replace#Syntax

0 Karma

johnhuang
Motivator

Splunk doesn't like fieldnames with special characters like periods.

 

| rename properties.url AS endpoint
| rex field=endpoint mode=sed "s/\/\d+\//\/{id}\//"

 

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...