All Apps and Add-ons

REST MODULAR INPUT APP global name 'raw_response_output' is not defined

mnaim
Explorer

Using the REST Modular Input App on my test box, I'm able to get json correctly displayed, but I get a different behavior when I deployed the app. I'm using a 6.0 Heavy Forwarder which forwards to 5.x Indexer. It works fine with the default response handler though. I have my custom response handler correctly showing in inputs.conf.

Looking at the logs, I see this:

"...ERROR ExecProcessor - message from "python /opt/splunkforwarder/etc/apps/rest_ta/bin/rest.py" NameError: global name 'raw_response_output' is not defined..."

My custom forwarder looks like this:

class MyCustomerJSONHandler:

def __init__(self, **args):
    pass

def __call__(self,response_object,raw_response_ouput,response_type,req_args,endpoint):

    if response_type == "json":
        output = json.loads(raw_response_output)
        for result in output["items"]:
            print_xml_stream(json.dumps(result))


    else:
        print_xml_stream(raw_response_output)
0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

There's a typo in your list of arguments, the parameter is declared as raw_response_ouput but used as raw_response_output.

View solution in original post

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

There's a typo in your list of arguments, the parameter is declared as raw_response_ouput but used as raw_response_output.

0 Karma
Get Updates on the Splunk Community!

Index This | Forward, I’m heavy; backward, I’m not. What am I?

April 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

A Guide To Cloud Migration Success

As enterprises’ rapid expansion to the cloud continues, IT leaders are continuously looking for ways to focus ...

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...