Getting Data In

Splunk REST API returns 500 when metadata inputs already exists

Craig1
New Member

Hi there, I'm using this API: https://splunk.github.io/splunk-add-on-for-amazon-web-services/APIreference/

Whenever I send a POST request to create metadata inputs that already exists, I get a 500 Internal Server Error.

Error: Unable to create metadata inputs: Unexpected HTTP status: 500 Internal Server Error (500)

Expected behaviour: Do not return 500, return a payload that indicates that the resource already exists.

Labels (1)
0 Karma

Craig1
New Member

Sorry I should also mention that this also happens with the roles endpoint which is where I got that message.

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Ok. First and foremost - do you have the addon installed?

Secondly - did you look what's in the logs?

0 Karma

Craig1
New Member

I'm just an API consumer, so not sure if I have the addon installed (do you have more specific instructions for me to pass on to the Splunk admin?).

As far as logs here is what I see:

<msg type="ERROR">
In handler 'splunk_ta_aws_iam_roles': bad character (52) in reply size</msg>
</messages>

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...