Getting Data In

External Lookup not passing argument contents to script

chartin
New Member

I have a external lookup that is not passing the search argument data to the script driving the lookup.

Here is my transform.conf:

[NotificationData1]
external_cmd = NotificationData.bat Notification
external_type = executable
fields_list = Notification, Notes, Summary, Severity, ClassName, InstanceName, EventName, EventText

I created a wrapper script which is the executable for the lookup:

set arg1=%1
D:\InCharge\CONSOLE\smarts\bin\sm_perl.exe HelloWorld.pl %arg1%

The search which drives this is passing one argument, Notification. This argument is a field from the search output:

| stats count
| eval Notification="NOTIFICATION-VoltageSensor_FaultPowerSupply210CiscoUCSChassis_I-VoltageSensorFaultPowerSupply210_CiscoUCSChassis-VOLT-BEM-10.7.15.5[ALBISC02CR-N4R3-FAB]/2/3356137/Chassis-2/Psu-4/210V_OutOfRange"
| table Notification
| lookup NotificationData1 Notification

My script is a perl program which I have defined logging to give me various messages as the script progresses. One of my first messages is to display the Notification argument from the lookup command.

No such luck. The perl script is reporting that I am getting them NAME of the argument, Notification not the value.

What could be the problem?

Any help at this point would be appreciated.

Tags (1)
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 ...