Splunk Search

Regex on input change

oriolcamp
New Member

In a dashboard, I have a dropdown input where the user can enter an IP address (customs value). I want to validate that the user's input is really an IP address/net and if not change it to 0.0.0.0/0. I have the following XML in the dropdown input:

<change>
    <eval token="net_token">if(match($value|s$,"\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}"),"OK","KO")</eval>
    <set token="net_token_exp">if(match($value|s$,"\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}"),"OK","KO")</set>
</change>

For example, I add the user custom value "aaaa" to the dropdown. Then, if I print the value of net_token_exp it shows:

if(match("aaaa","\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}"),"OK","KO")

But maybe the net_token value is OK (even if it does not match the regex...) or it even not evaluates the condition so it does not change the net_token value.

What am I doing wrong?

0 Karma

DalJeanis
Legend

The set would not evaluate the string, so that won't work.

For test purposes, check this...

 <eval token="net_token_test1">$value|s$</eval>
 <set token="net_token_test2">$value|s$</set>
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!

At .conf26, Don’t Just See What’s Next. Help Shape It at Innovation Labs.

Long before a new capability reaches the keynote stage, it begins as an idea waiting to be tested. At ...

Forwarder Topology Guidance: Intermediate HF vs Intermediate UF

Why Universal Forwarders Should Not Be Used as Intermediate Forwarders A practical Splunk forwarding topology ...

Data Management Digest – August 2026

Data Management Digest   Welcome to the August 2026 edition of Data Management Digest! August was a big month ...