Splunk Search

How can I use a variable as parameter for a custom command?

HustenHelmut334
New Member

This is not working: Is there a special syntax to use the content of a variable an not its name?

sourcetype="test"
|stats
|eval minute=tonumber(strftime(_time,"%M"))
|eval foo=250
|eval th=if(minute > 30,"foo=100:200","foo=0:0")
|addinfo
|mycustomcommand monitor=test defaults="foo=150" thresholds=th

This working:

|mycustomcommand monitor=test defaults="foo=150" thresholds="foo=100:200"    

Why is th not evaluated?

0 Karma

woodcock
Esteemed Legend

Try this:

sourcetype="test"
|stats
|eval minute=tonumber(strftime(_time,"%M"))
|eval foo="250"
|eval th=if(minute > 30,"foo=100:200","foo=0:0")
|addinfo
| map search="|mycustomcommand monitor=test defaults=\"foo=$foo$\" thresholds=\"$th$\""
0 Karma

woodcock
Esteemed Legend

Try this @spammenot66 and @HustenHelmut334.

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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

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

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...