Getting Data In

Python SDK [list of inputs in input.conf]

fklink
New Member

Hi,

i have 40 inputs [type: monitor] configured in one inputs.conf. Let's call them 001, 002, 003, .... 040

i'm using python sdk to list all available inputs which are configured in inputs.conf file.

As splunk documentation describes i'm using :

for item in inputs:
print ("%s (%s)" % (item.name, item.kind))

Unfortunately splunk lists only the first 37 entries. It looks like:
/path......../001 (monitor)
/path......../002 (monitor)
/path......../003 (monitor)
....
/path......../037 (monitor)

If i use console splunk list monitor i can see all inputs (001 ... 040). Also on web-ui all inputs are there.

If i delete one input (e.g. 002) and list again using

for item in inputs:
print ("%s (%s)" % (item.name, item.kind))

Splunk shows me:
/path......../001 (monitor)
/path......../003 (monitor)
....
/path......../038 (monitor)

So it look's like, python sdk collects only the first 37 listings of inputs.

Is this a known issue? What am I doing wrong?

Many thanks in advance

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...