<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Python SDK example inputs.py not returning all inputs in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Python-SDK-example-inputs-py-not-returning-all-inputs/m-p/602461#M10661</link>
    <description>&lt;P&gt;I'm trying to do a little testing of our Splunk installation and I am looking at the Python SDK examples.&amp;nbsp; I've run the inputs.py script hoping it would get me a list of all the inputs defined in our inputs.conf but it only seems to return a small subset.&amp;nbsp; I don't see any logic as to why it is returning the subset it does.&amp;nbsp; I get about 30 records back from inputs.py. I expect well over 100.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Running "splunk btool inputs list" gives me the set I expect, but I don't want to have to run this locally.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any rules or restrictions to the Python SDK API to get the list of inputs?&amp;nbsp; Maybe some options missing in the sample to get the defined inputs list?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rob.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 20 Jun 2022 18:42:40 GMT</pubDate>
    <dc:creator>rmjohns</dc:creator>
    <dc:date>2022-06-20T18:42:40Z</dc:date>
    <item>
      <title>Python SDK example inputs.py not returning all inputs</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Python-SDK-example-inputs-py-not-returning-all-inputs/m-p/602461#M10661</link>
      <description>&lt;P&gt;I'm trying to do a little testing of our Splunk installation and I am looking at the Python SDK examples.&amp;nbsp; I've run the inputs.py script hoping it would get me a list of all the inputs defined in our inputs.conf but it only seems to return a small subset.&amp;nbsp; I don't see any logic as to why it is returning the subset it does.&amp;nbsp; I get about 30 records back from inputs.py. I expect well over 100.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Running "splunk btool inputs list" gives me the set I expect, but I don't want to have to run this locally.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any rules or restrictions to the Python SDK API to get the list of inputs?&amp;nbsp; Maybe some options missing in the sample to get the defined inputs list?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rob.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2022 18:42:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Python-SDK-example-inputs-py-not-returning-all-inputs/m-p/602461#M10661</guid>
      <dc:creator>rmjohns</dc:creator>
      <dc:date>2022-06-20T18:42:40Z</dc:date>
    </item>
    <item>
      <title>Re: Python SDK example inputs.py not returning all inputs</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Python-SDK-example-inputs-py-not-returning-all-inputs/m-p/602464#M10662</link>
      <description>&lt;P&gt;As an addendum,&amp;nbsp; the rest API returns the same results, which makes sense since I assume the SDK is just a wrapper for that.&amp;nbsp; ie, using:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;curl https://splunk-dev1:8089/services/data/inputs/monitor&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;also only returns a small subset of my expected inputs.&amp;nbsp; And currently, the inputs I'm looking for are all "monitor" type of inputs.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2022 22:35:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Python-SDK-example-inputs-py-not-returning-all-inputs/m-p/602464#M10662</guid>
      <dc:creator>rmjohns</dc:creator>
      <dc:date>2022-06-20T22:35:13Z</dc:date>
    </item>
  </channel>
</rss>

