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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...